SQL 2008 has some key improvements over SQL 2005. This article deals with backup compression and faster backups in SQL 2008
Your job is to scan the trades data and identify combination of trades that match a given rollup data.
An open call to the amatuers that might want to pen some database related cartoons for Simple Talk Publishing.
Should we really avoid cursors? See how to rewrite code to avoid cursors and also analyze the implications.
Today Steve Jones asks how you handle those passwords across time for backups in this week's Friday poll.
This guide outlines the major considerations that must be taken into account when onboarding Microsoft® SQL Server® environments into a private cloud infrastructure.There is a strong trend in IT to virtualize servers whenever possible, driven by:1. Standardization2. Manageability3. IT agility and efficiency4. Consolidating servers reduces hardware, energy, and datacenter space utilization costs5. Virtualized environments allow new Disaster Recovery strategiesThe Hyper-V™ role in Windows Server® 2008 R2 provides a robust and cost-effective virtualization foundation to deliver these scenarios.However, there is significant risk in virtualizing SQL Server environments without giving careful consideration to the workloads being virtualized and the requirements of the server applications running on a Hyper-V environment.
Gain an insight into how to use your SQL Server cluster for more than just high availibility in this article from Mark Jones.
Can greedy executives be good for IT? Steve Jones thinks so and gives us a few reasons today.
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...
By Arun Sirpal
Not every production incident is a database in RECOVERY_PENDING or a corrupted event (like...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Hi All I am trying to find 'bad' characters that users might type in....
Comments posted to this topic are about the item Extreme DAX: Take your Power...
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