SQL Server Disasters with Preventive Measures
Have you seen disasters in your environment? I would bet you have at some point. Let's see if our top 13 disasters matches your experiences.
Have you seen disasters in your environment? I would bet you have at some point. Let's see if our top 13 disasters matches your experiences.
I see, with some relief that the threatened removal of Rules and Defaults in SQL Server 2008 hasn’t happened. There has been a stay of execution. Even though they are documented, they still come with a dire warning that they are deprecated and will be removed in future versions. They have fallen foul of the SQL Standards committee, and we are now supposed to use check constraints instead.
Steve Jones is taking well-earned break. In his guest editorial slot, Brad McGehee discusses three simple techniques to help DBAs manage their time more effectively.
This article from new author Peter Kierstead shows us how to implement your own "fuzzy" dedup/merge logic without resorting to RBAR in T-SQL.
This tutorial walks you through the process of adding SQL statements to your SSIS packages and bundling them into logical units of work if necessary.
This article describes how the Transparent Data Encryption feature in SQL Server 2008 can be used to secure your databases
One of the few things that SQL Server does not automatically help you with is the design of your tales, views, and other database objects. Having standards and design techniques can greatly ease the maintenance of your schema as well as ease the transition to having others work with the database. New author J.D. Gonzalez brings us some of his naming techniques to keep things organized.
Calling all developers! Does the idea of going from a concept to a prototype in a 54 hour marathon weekend of design and coding sound fun to you? If so, join us!
By using cascading referential integrity constraints, you can define the actions that SQL Server 2005 takes when a user tries to delete or update a key to which existing foreign keys point.
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