Additional Articles


Technical Article

Write custom trace files in TSQL

SQL Server 2005's default trace is great for monitoring system information and for finding out what happened on your server after problems occur. However, there are times when the events that the default captures are not what you need. Here are instructions for how you can create your own trace files in TSQL to catch events on your database machine.

2007-10-08

3,101 reads

Blogs

From Data Custodian to Innovation Catalyst: The Evolving Role of the CDO

By

There was a time when the Chief Data Officer lived in the shadows of...

Down the Rabbit Hole: Dealing with Ad-Hoc Data Requests

By

"But I don’t want to go among mad people," Alice remarked."Oh, you can’t help...

Adding a Local Model to Ollama through the GUI

By

I saw some good reviews of the small gemma3 model in a few places...

Read the latest Blogs

Forums

Parameter sniffing issue with different minutes as opposed to using midnight

By mikael_ljunghorn

Hej, I'm not facing this issue but as I was working another parameter sniffing...

Some query values change when query is run but not others. Why?

By water490

Hi everyone I have a 1000 line SQL query that is too long to...

using different credentials when debugging ssis

By stan

hi, now and then i want one connection in my ssis pkgs to use...

Visit the forum

Question of the Day

PWDCompare

What does the PWDCOMPARE function do?

See possible answers