Technical Article

An Overview of SQL Server 2005 for the Database Developer

With the release of Microsoft SQL Server 2005 Beta 2, the world of database development is changing. As a database developer, you now have the option to appropriately locate your code in relation to its functionality, to access data in native formats such as XML, and to build complex systems that are driven by the power of the database server. Database development is becoming more integrated than ever before, and all of the tools that you need are available right at your fingertips.

SQLServerCentral Article

Identifying Blocking Locks

Blocks in SQL Server can cause untold amounts of pain and headache, mostly because they are so transient and often when you go to look for them, they have been released on whatever object you are researching. Author Eli Leiba has writeen a short piece on how you can automate the search for blocking locks and help you as a DBA be proactive in identifying them.

SQLServerCentral Article

Manipulating And Using DateTime Data

Working with date and time data in SQL Server can be a bit cumersome using just T-SQL. With the separate datatypes being pulled from SQL Server 2005 for the time being, however, it is something that a DBA needs to get used to. Robert Marda brings us an instructional look at the different datetime data types and some things you should be aware of when developing with them.

SQLServerCentral Article

Controlling SQL Server Settings

Change control in SQL Server isn't the strong point of the product. And change control of server based settings is something that you might not worry about, but which can easily cause you hours of troubleshooting time. Author Andre Vigneau deploys software to other companies and has developed a solution to deal with this problem. Read on and get some code that can help you prevent or at least fix any changes to SQL Server sp_configure parameters.

Blogs

Fabric for Operational Reporting & SQL Endpoint Trap

By

With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...

Crawl, Walk, Run with Agentic Development of Power BI Assets

By

If you’ve been watching AI roll through the data community and thinking, “this seems...

How AgentDBA Diagnoses SQL Server Issues Fast

By

Not every production incident is a database in RECOVERY_PENDING or a corrupted event (like...

Read the latest Blogs

Forums

SQL Art, Part 4: Happy 4th of July — A British DBA's Guide to Celebrating a War We Don't Talk About

By Terry Jago

Comments posted to this topic are about the item SQL Art, Part 4: Happy...

Finding 'bad' characters

By Barcelona10

Hi All I am trying to find 'bad' characters that users might type in....

Extreme DAX: Take your Power BI and Fabric analytics skills to the next level

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Extreme DAX: Take your Power...

Visit the forum

Question of the Day

Changing the Schema

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
GO
I 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
GO
This worked. Now, I move this schema to a new user.
ALTER AUTHORIZATION ON SCHEMA::Myschema TO User3;
GO
What happens with this code?
SETUSER 'USER2'
GO
SELECT * FROM MySchema.MyTable
GO

See possible answers