Using Xp_cmdshell
One of the most handy extended stored procedures in SQL Server is xp_cmdshell. This article will show you how to use it.
2003-11-14 (first published: 2001-05-03)
39,695 reads
One of the most handy extended stored procedures in SQL Server is xp_cmdshell. This article will show you how to use it.
2003-11-14 (first published: 2001-05-03)
39,695 reads
This article by Andy Warren talks about using sp_addlogin to move logins from one server to another. It also points out a problem you may run into if you have a SQL 7 server that was upgraded from 6.5
2007-10-02 (first published: 2001-05-01)
10,938 reads
How can you maintain a stable environment? Keeping track of all changes is the time-tested and proven technique. Read about it here.
2001-04-30
5,436 reads
This article shows you in a step-by-step manner how to restore the master database.
2001-04-29
8,966 reads
The eighth part of Steve Jones's series on having SQL Server automatically report information to a DBA.
2001-04-29
6,710 reads
Everyone needs a stable environment. This article discussed ways to keep your team on the same page.
2001-04-25
5,818 reads
The sixth part of Steve Jones's series on having SQL Server automatically report information to a DBA.
2001-04-25
5,684 reads
The fifth part of Steve Jones's series on having SQL Server automatically report information to a DBA.
2001-04-24
7,007 reads
The fourth part of Steve Jones's series on having SQL Server automatically report information to a DBA.
2001-04-22
5,961 reads
Nothing is more annoying than having to disconnect users one by one. With this script, you will be able to quickly disconnect them with a few keystrokes.
2001-04-21
18,240 reads
By Steve Jones
It’s Prime Day. A few of my recommendations, since I want to do some...
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
If you’ve been watching AI roll through the data community and thinking, “this seems...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Hi All I am trying to find 'bad' characters that users might type in....
Comments posted to this topic are about the item Extreme DAX: Take your Power...
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