Working with the Registry
It's not often you'll need to access the registry from SQL, but when you do - these functions make it happen!
It's not often you'll need to access the registry from SQL, but when you do - these functions make it happen!
A week ago, we solicited readers to let Microsoft know which of the SQL Server 2005 announced features mattered most to them. We had a great response, with 890 of you answering the survey in three days. The answers were pretty interesting. The full results can be seen at the bottom of this article.
Some good info on password changes in Yukon (SQL 2005). Based on the beta, but worth taking a look at.
Dinesh did a little research on nulls and was kind enough to package it up for us. How many of you know or use NULLIF? Or COALESCE? Handy stuff!
We saw a note from Chad about a tool he wrote in the forums and asked him to write up some notes. Not only did we get notes, we got the source code! See what a DBA can do with some DMO.
We get books in occasionally for review and have started making them available to our existing authors. Jim was interested in this one - turns out he didn't find much to like. If you're a beginner it might be a better fit. Or maybe you've read the book and disagree?
A very short article that discusses how nulls can ruin your day if you don't understand how they behave when you concatenate.
We had Mike take a look at this product recently and he found a lot to like. He also had some suggestions about ways the product could be improved - interesting since you get free upgrades for life with this product. This is a very good walk through of the product.
Microsoft confirmed today that it has delayed Yukon yet again. It also announced that Yukon has an official name and will have another beta added to the development cycle. Get all the info here and share with Microsoft your thoughts about what features are important to you.
Regular columnist Chris Hedgate follow up on Andy's recent article about Worst Practices with one of his own. This is worth passing on to your development team.
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