More Tips for New (and old) DBAs
Following up on the popular article: Tips for New DBAs, author Craig Outcalt tackles three more issues including customer support and why you should learn T-SQL.
Following up on the popular article: Tips for New DBAs, author Craig Outcalt tackles three more issues including customer support and why you should learn T-SQL.
Today we have a guest editorial from Andy Warren. Today Andy talks about his changing role as a DBA and how many tasks he doesn't need to handle anymore.
SQL Server 2014 offers In-Memory OLTP, but you may be hesitant to use this because of the lack of support for constraints on Memory-Optimized Tables. In this tip we will see how we can solve these issues.
Learn how to incorporate Test-Driven Development practices into your database development methodology with TSQLUnit.
SQL Saturday is a training event for SQL Server professionals and those wanting to learn about SQL Server. This event will be held Dec 13 2013 at Università Politecnica delle Marche - Ancona, Italy. This SQL Saturday will feature 3 tracks focused on BI, DBA, and Development.
A classic article by Gerg Larsen explaining how and how not to use a function within your T-SQL statements. Where you place your function within your T-SQL statements determines how your query will be processed and can severely impact the query execution plan and the performance of your query.
Today we have a guest editorial from Andy Warren. There are often issues with how we get along with each other at work. Andy asks how you might handle a tough decision over a simple problem.
For loading text, CSV or XML files into SQL Server, the Log Parser utility, with its amazing SQL engine, is likely to be the obvious choice. Although initially developed purely for converting IIS logs, the Log Parser can turn its hand to a range of formats including even event logs or the Windows registry.
This Friday Steve Jones has a poll about developers. Help compile a good list of common mistakes made in SQL Server.
It is Friday, the queries are running, and nobody is watching the bill. That...
By Steve Jones
Annabel retired from Redgate Software this week. Across most of my career at Redgate,...
By Tim Radney
As a SQL Server DBA with years of experience tuning production environments, I’ve seen...
Comments posted to this topic are about the item What is the Cloud?
Comments posted to this topic are about the item Changing the Schema
Comments posted to this topic are about the item Index Fragmentation Explained: Page Splits,...
I set up a few users on my SQL Server 2022 instance.
CREATE LOGIN User1 WITH PASSWORD = 'Demo12#1' CREATE USER User1 FOR LOGIN User1 GO CREATE LOGIN User2 WITH PASSWORD = 'Demo12#2' CREATE USER User2 FOR LOGIN User2 GO CREATE LOGIN User3 WITH PASSWORD = 'Demo12#3' CREATE USER User3 FOR LOGIN User3 GOI then created a schema that one of them owned. Under this schema, I added a table with some data.
CREATE SCHEMA MySchema AUTHORIZATION User1
GO
CREATE TABLE Myschema.MyTable(myid INT)
GO
INSERT MySchema.MyTable
(
myid
)
VALUES
(1), (2), (3)
GO
SELECT * FROM MySchema.MyTable
GO
I granted rights and verified that User2 could access this table.
GRANT SELECT ON Myschema.MyTable TO User2 GO SETUSER 'USER2' GO SELECT * FROM MySchema.MyTable GOThis worked. Now, I move this schema to a new user.
ALTER AUTHORIZATION ON SCHEMA::Myschema TO User3; GOWhat happens with this code?
SETUSER 'USER2' GO SELECT * FROM MySchema.MyTable GOSee possible answers