Stairway to Server-side Tracing - Level 1 - Overview of Tracing
The first part of our stairway series on SQL Trace examines the overview of this subsystem in SQL Server, it's architecture and the kind of information it returns.
The first part of our stairway series on SQL Trace examines the overview of this subsystem in SQL Server, it's architecture and the kind of information it returns.
Compares and contrasts tracing using Profiler with server-side tracing, illustrating important performance differences so that one can choose the right tool for the task at hand.
This is the second article in our Stairway Series on SQL Tracing. Learn how to build traces in code with T-SQL.
This is the second article in our Stairway Series on SQL Tracing. Learn how to build traces in code with T-SQL.
In this third article of our Stairway Series on tracing, Dan Guzman goes into the method of using Profiler to help you create a custom trace of the events that you need to monitor.
In this third article of our Stairway Series on tracing, Dan Guzman goes into the method of using Profiler to help you create a custom trace of the events that you need to monitor.
An introduction to the SQL Server default and black box traces targeted at DBAs who are new to these specialized traces. The article shows how to enable and disable the default trace feature and create a black box trace. The captured events are discussed along with how to view current and historical trace data of these traces.
An introduction to the SQL Trace catalog views and functions used to view existing trace definitions targeted at DBAs and Developers. The article discusses T-SQL queries to view defined traces, query trace status and start/stop/delete traces.
How to import a trace file into a table using T-SQL and the Profiler tool, for subsequent ad-hoc analysis.
How to use SQL Jobs, scripts and SSIS to manage traces and trace data collection.
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...
Because we are NABL Accredited Laboratories, our personal care and cosmetics research center provides...
WhatsApp:0817-866-887 Jl. Ahmad Yani No.31, Pattunuang, Kec. Wajo, Kota Makassar, Sulawesi Selatan 90174 (@bcakcumakassar)
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