Audit Trails and Logging Part II
Continuing with Part II of his auditing series, Gsquared takes a look at active auditing techniques for your SQL Server.
Continuing with Part II of his auditing series, Gsquared takes a look at active auditing techniques for your SQL Server.
Steve Jones talks about IT Project Failure and how you should re-evaluate things are you move forward.
When Nigel Rivett takes us on a tour of the apparently innocuous subject of Identity Columns in TSQL, even the seasoned programmer is due for one or two surprises.
Profiler is a tool that monitors the events and activity running on a SQL Server. Using profiler, this monitoring can be viewed, saved, and replayed. This article focuses on using Profiler with SQL Server 2005, but the tool is also included with SQL Server 2000 and SQL Server 2008.
Having separate databases for each client? It's a common problem and Steve Jones wonders if this might be a feature coming in SQL Server at some point.
Auditing becomes more important every day as new requirements for data access are implemented. New author Gsquared, well known in the forums, brings us a look at types of audits and some details on passive auditing techniques.
The other day, I was chatting to a keen PostgreSQL user. We're used to having free databases, such as IBM DB2 Express-C, Microsoft SQL Server 2005 Express Edition, SQLite and Oracle XE, but PostgreSQL is different in that it is open source. It is a proper, dedicated community too, I was told...
SQL Server Management Studio is rich with features. So rich, in fact, that after almost 3 years I am still finding new tools in the application that afford me more control over my databases and the methods for supporting them. Recently I found myself needing to script out a database and its objects for reviewing a problem offline.
Steve Jones talks about IT Project Failure and how you should re-evaluate things are you move forward.
Steve Jones talks about IT Project Failure and how you should re-evaluate things are you move forward.
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