SQL Server 6.5: Index Statistic Details
This article examines how index statistics are used in SQL Server 6.5
2001-10-30
3,316 reads
This article examines how index statistics are used in SQL Server 6.5
2001-10-30
3,316 reads
One of the largest security "issues" in SQL Server 7.0 is that a user must be in the SysAdmin role to run the BULK INSERT command. This article by Paul Ibison shows you a workaround.
2001-10-30
6,202 reads
Article number four in this popular series continues exposing Worst Practices! This week Andy continues his tirade by talking about why case sensitive databases should be BANNED from the planet. Is he right or just OUT OF CONTROL? Read the article and join the discussion - your comment may lead to an article, that's what generated this one!
2005-07-08 (first published: 2001-10-29)
29,262 reads
This article looks at some of the undocumented DBCC commands that exist in SQL Server 7.0
2001-10-22
7,553 reads
Have you ever experienced a T-SQL query, a stored procedure, view or a trigger returning unexpected results. In this article by Raj Gill, he shows you how ANSI DEFAULTS may be to blame.
2001-10-18
10,843 reads
Running a script automatically from SQL Server is easier than you think. Here are a few methods you can use.
2001-10-17
17,470 reads
This article covers some of the common issues and questions when you cluster SQL Server 2000 and Windows 2000.
2001-10-11
13,672 reads
The Web Data Administrator is a utility program implemented in ASP.NET that enables you to easily manage your SQL data, wherever you are.
2001-10-10
1,911 reads
In this article, Alexander Chigrik looks at some useful undocumented stored procedures that shipped with SQL Server 2000.
2008-10-17 (first published: 2001-10-08)
30,232 reads
This article examines some of the undocumented stored procedures that exist in SQL Server 7.0
2001-09-28
7,777 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...
WhatsApp:0818-751-777 Jl. Kalierang No.Ruko 3-5, Dukuhturi, Kec. Bumiayu, Kabupaten Brebes, Jawa Tengah 52273 (@bcakcpbumiayu)
WhatsApp:0818-751-777 Menara Satu Sentra Klp. Gading, Jl. Boulevard Bar. Raya No.1 Lt. Dasar, 1,...
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