We all know that you should try to size tempdb appropriately, so it doesn’t need to autogrow shortly after starting up SQL Server. It isn’t always easy to do this. Therefore, when you first implement a new server and/or add new databases you should monitor the autogrowth events on tempdb. By monitoring the autogrowth events you can easily determine if you have sized tempdb appropriately.
2018-07-17
2,946 reads
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.
2012-04-05
3,916 reads
By Brian Kelley
In information security (INFOSEC), there several foundational concepts and principles. One of the ones...
By Steve Jones
the standard blues– n. the dispiriting awareness that the twists and turns of your...
By Chris Yates
A brief introduction to the tool and its advantages for database migrations DevOps is...
I'm tracing activity on one database and would like to include the client_app_name in...
select Custno, Addr1, City, Res_Phone, Bus_Phone, Fax_Phone, Marine_Phone, Pager_Phone, Other_Phone, email1, email2 from customer...
I'm only processing 50,000 records not everything from the Table where there are 250,00...
I want to mark a transaction in the log as a recovery point. How do I do this in my code if I use the transaction, myTran?
See possible answers