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
This month, I prompted bloggers to discuss whether good enough is perfect. Thank you to all...
By Steve Jones
Recently a customer asked if SQL Compare and SQL Data Compare can be used...
I have an application team that is insisting on daily (and for some, weekly)...
i see this in the definition of a linked server on our wh sql...
Is this even possible ? Tried with grant but to no avail. [sys].[database_role_members] and...
What does this code return in SSMS 20 from SQL Server 2019?
select '|' + CHAR(0)+'abc' + '|';See possible answers