The New Year - 2009
It's the first day of 2009 and Steve Jones gives a few predictions for the new year in this editorial.
It's the first day of 2009 and Steve Jones gives a few predictions for the new year in this editorial.
It's the first day of 2009 and Steve Jones gives a few predictions for the new year in this editorial.
In a previous tip on Disaster Recovery Procedures in SQL Server 2005 Part 1, we have seen how we can come up with a disaster recovery procedure in SQL Server 2005. There are other ways to increase availability of your highly critical database in SQL Server 2005. What are those other options?
Moving databases is fairly simple, but when you move a system database, there are a few extra steps to follow. MVP Brian Knight walks us through how to move temdb in this video.
What would you do if you want to perform 15 to 30 lookups using the same reference dataset? This is how I did it...
Steve Jones gives one last update on energy issues in the US in 2008 with a look at the construction and building industries.
Today many companies determine to publish their data on the Internet trying to expand their business and make their information more accessible. The IT industry proposes a wide range of original solutions for resolving data inconsistency problems that publishers inescapably face when exporting their data as they need to properly access, process and interchange large amounts of information mainly through the web.
Yan Pan explains how to set up proxies in SQL Server 2000, 2005 and 2008, and compares the differences between them
SQL Bits IV, in Manchester, UK next year on March 28th, is now looking for speakers. Please submit a session if you are interested.
Steve Jones is considering changes to SQLServerCentral and presents a few ideas today.
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