READ Data from default Trace
READ Data from default Trace to know when the objects are altered. If no database name is provided, it will run through all the databases.
2019-05-03 (first published: 2015-04-08)
1,412 reads
SQL Trace
Automating SQL Traces
Capturing the activity on a server when a problem occurs can be a challenge for many DBAs. This article shows how you can automate the capture of information when a CPU spike occurs.
2013-05-23
6,430 reads
The default trace in SQL Server - the power of performance and security auditing
Since the introduction of SQL Server 2005, there is a simple lightweight trace that is left running by default on every SQL Server. This provides some very valuable information for the DBA about the running server, but it isn't well-documented. Feodor Georgiev reveals many of the secrets of this facility and shows how to get reports from it.
2011-03-28
3,896 reads
Stairway to Server-side Tracing
Learn how to use the SQL Trace subsystem in SQL Server to audit your instances. This series will examine the basics of SQL Trace and teach you how to set up, schedule, and manage traces and the data generated.
2019-03-26 (first published: 2011-02-01)
3,381 reads
Auto Generate an Hourly SQL Server Profiler Trace File
I would like the option on some servers of having a profiler trace running 24x7 in the background. I could then access and read these trace files to investigate issues after the fact - much like the default trace that came out with SQL 2005.
2009-09-29
3,975 reads
Default Trace Load of All 5 Files
The default trace keeps the last 20 meg of info, and a max of 5 files...This loads all 5 files into a table so it can be reviewed.
2009-02-25 (first published: 2009-02-07)
1,249 reads
2008-12-26
2,989 reads
2008-12-08
2,489 reads
Blogs
Advice I Like: Art
By Steve Jones
Superheroes and saints never make art. Only imperfect beings can make art because art...
Why Optimize CPU for RDS SQL Server is a game changer
One feature that I have been waiting for years! The new announcement around optimize...
Performance tuning KubeVirt for SQL Server
Following on from my last post about Getting Started With KubeVirt & SQL Server,...
Forums
The AI Bubble and the Weak Foundation Beam
Comments posted to this topic are about the item The AI Bubble and the...
data type gets lost in data flow
Hi, in a simple oledb source->derived column->oledb destination data flow, 2 of my...
i noticed the sqlhealth extende event is on by default , so can i reduce
hi, i noticed the sqlhealth extended event is on by default , and it...
Question of the Day
The Read Committed Snapshot Isolation behaviour
I am currently working with Sql Server 2022 and AdventureWorks database. First of all, let's set the "Read Committed Snapshot" to ON:
use master; go alter database AdventureWorks set read_committed_snapshot on with no_wait; goThen, from Session 1, I execute the following code:
--Session 1 use AdventureWorks; go create table ##t1 (id int, f1 varchar(10)); go insert into ##t1 values (1, 'A');From another session, called Session 2, I open a transaction and execute the following update:
--Session 2 use AdventureWorks; go begin tran; update ##t1 set f1 = 'B' where id = 1;Now, going back to Session 1, what happens if I execute this statement?
--Session 1 select f1 from ##t1 where id = 1;See possible answers