Tracking Business Metrics
There can be more to managing a SQL Server instance than just examining the performance metrics. There are times when understanding how your system is performing for the application is important.
There can be more to managing a SQL Server instance than just examining the performance metrics. There are times when understanding how your system is performing for the application is important.
The concept of a sliding window scenario is to manage and keep the same number of partitions on a partitioned table over time. Learn how in this step-by-step from Arshad Ali.
Overview of 2 very important clauses added to SELECT statement in SQL2012 to allow paging on result sets.
What's important in an IT employee? Steve Jones talks about the skills and measurements CIOs want today and tomorrow. Today's editorial was originally released on July 22, 2008. It is being re-published as Steve is at SQL Intersection.
We need to exclude SQL Server database files from Antivirus and Third Party Backup Software (to make sure that files are not accessed directly). How can we be sure that all of our SQL Server file extensions are using the standard file extensions for database files?
Does your IT organization bring value to your company? Steve Jones takes a look at some of the ways you can do this. This editorial was originally published on July 2, 2008. It is being re-published as Steve is at SQL Intersection.
Microsoft Database Engine Tuning Advisor (DTA) is a database performance tuning utility designed to analyze your SQL Server database and suggest actions to be taken in order for taking your query performance to the next level.
Alex talks through a simple practical example of a database deployment, First creating a empty database and then upgrading it through three steps by writing T-SQL scripts, adjusting configuration files and the change log, before generating a full build script containing all schema objects.
Sometimes auditing for one certification might help you pass another, but don't count on it.
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...
It is Friday, the queries are running, and nobody is watching the bill. That...
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