Technical Article

A Few Cool Things You Can Identify Using the Default Trace

If you are running an instance of SQL Server 2005 and above then most likely that instance is running the default trace. This default trace is a canned Profiler server side trace that automatically starts up when SQL Server starts. In this article Greg Larsen explains more about the default trace and shows you how to glean some event information from the trace files created by this background trace process.

External Article

Using Friendly Names for SQL Servers via DNS

Wouldn't it be great if your HR folks only had to put in HR-SQL.mydomain.com for the database connection in their reports? They wouldn't have to remember it was on server Nile and they certainly wouldn't have to change their reports if you migrated their database from the Nile server to the server named Danube. In DNS there are two easy ways to do this.

Blogs

Excellent article on securing msdb

By

Fabiano Amorim has written an excellent article at Simple Talk on securing msdb. Here's...

T-SQL Tuesday #201: Temp Tables

By

This month we have a new host, which I am grateful for. So many...

When Do You Reach For A #temp Table?

By

I needed to do some research because there is more to #temp tables than...

Read the latest Blogs

Forums

jdbc auth failing to sql from sap's cloud middleware CPI

By stan

hi , our business partner is asking s4 sap api's for receivable info and...

Searching for my own posts

By pietlinden

I have a really stupid question... Is there an easy way to search for...

How to Work with On-Premises AI Models to Generate T-SQL Code

By Daniel Calbimonte

Comments posted to this topic are about the item How to Work with On-Premises...

Visit the forum

Question of the Day

Escaping Strings

The STRING_ESCAPE() function requires 2 parameters in SQL Server 2025. The first is a string of text and the second is the type of escape rules being used. What are the options for the second parameter?

See possible answers