A Brute Force Way to Compress a Database
There are a handful of scripts out there to compress all of of the objects in your SQL 2008 database...
There are a handful of scripts out there to compress all of of the objects in your SQL 2008 database...
By quickly and easily obtaining the identity value, the OUTPUT clause of an INSERT statement can obtain the auto-generated identity value of a row, and so will allow the application to immediately reference the new row or add rows to another table that use the identity value as a foreign key reference.
Phil Factor finds much to admire in Microsoft's new Orchard application but is frustrated by a design decision that seems to limit its use to low-volume applications, with less stringent security requirements.
A two-year project involving a team of 15 people, a Future of Monitoring blog, input from thousands of IT professionals, and hundreds of hours brainstorming about how the world is changing has led to Red Gate’s newly released SQL Monitor.
Today we have an older editorial by Steve Jones being republished. This piece talks about security and why it might be a good idea to write down those passwords.
Unlike fine wine, you typically wouldn’t want your statistics to be aged. At least for tables that are being updated...
I'm needing to audit the permissions in my databases, but I want to script them out so I have something to run in case of a recovery situation. I've got the logins, roles, and users handled, but it's the permissions that I want to extract. How can I do this easily?
In this next installment of his series on TDD, MVP Andy Leonard continues the development of his database.
This Friday Steve Jones asks the question about how you manage large numbers of SQL Server instances.
Your application code may look neat and clean, and you are using a sound Object-relational Mapper, but when you put the pedal to the metal, you're not getting the performance. The time has come to lift the hood and see what SQL is being generated by the ORM, and what part of your code is causing the bottlenecks. The effect can be spectacular.
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