Review of SQL2K Resource Kit
Good enough for your bookshelf? This one meets that requirement for Brian, click the link to find out why.
Good enough for your bookshelf? This one meets that requirement for Brian, click the link to find out why.
According to this article Mangione will be working on security products. Paul Flessner and several other managers will take over the SQL team.
Leo reviews a new product as a follow up to his recent article about Monitoring Failed Job Steps.
This article shows some options to retrieve all the metadata you'll need to write scripts that write scripts. No, that's not a goof, this article is about code generation.
Probably not a task you'll have to do very often, all the better that someone has laid out how to do it in good detail!
If you are (or want to be) a power user, this book should be on your shelf. How many books have you read that have you using a debugger to step into the sql server process? James gives it a thumbs up!
One of the strengths of Visual Studio .NET is its features for rapid application development, or prototyping. If, for example, you want to develop a Windows form that lets you maintain the data in one table of a database, you can usually do that in 20 minutes or less. This article will show you how.
Do you have the need for more speed on your servers? How do you go about squeezing more speed out of the database when faced with an upgrade? Steve Jones walks through some of his thought process when looking at ugprade for one of his servers.
As Jeff says, "There are lots of articles about how to do auditing, but there are few discussions about how to use the auditing results in a real time environment". Well, now we have one that shows you how to do it!
Nice write up on the Admin Companion. Should you add it to your bookshelf? Frank offers his frank opinion.
By Arun Sirpal
Not every production incident is a database in RECOVERY_PENDING or a corrupted event (like...
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,...
Comments posted to this topic are about the item Extreme DAX: Take your Power...
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
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