A Lack of SQL
Steve Jones talks about a company looking to write all their stored procedures using the CLR in SQL Server. Is this a good idea?
Steve Jones talks about a company looking to write all their stored procedures using the CLR in SQL Server. Is this a good idea?
A bug in the SQL Server 2008 upgrade process has Steve Jones questioning the coding practices at Microsoft.
Working with filegroups and managing the location of your various objects can be a cumbersome task in SQL Server. New author Thom Bolin brings us a technique and some code that worked well for one of his clients.
One of the things I typically need to do is to collect performance data on the server which includes CPU, memory and disk utilization as well as SQL Server-specific data. What command line tools are available to do this?
Murphy’s Law tells us that whatever can go wrong will go wrong. This axiom applies to all aspects of life, including data warehousing. The following corollaries to Murphy’s Law relate this inevitability of something going “bump” in the night to data warehousing.
A new data mining thrilled from Jeffrey Deaver has Steve Jones concerned about the centralization of data mining.
A new data mining thrilled from Jeffrey Deaver has Steve Jones concerned about the centralization of data mining.
A new data mining thrilled from Jeffrey Deaver has Steve Jones concerned about the centralization of data mining.
A series of online conferences covering various aspects of SQL Server and other Microsoft technologies. Check out the list for this fall and see if there is some training that you can attend.
Steve Jones talks about a company looking to write all their stored procedures using the CLR in SQL Server. Is this a good idea?
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