Squeezing Wasted Full Scans out of SQL Server Agent
This article by new contributing member Bob Musser shows you how to reduce the amount of scans that SQL Server Agent does against databases. Not for the faint of heart.
2003-02-13
4,964 reads
Bob Musser
Blogs
Why use XACT_ABORT?
This came up one day at my work when a developer was using it....
Using AI for Data Conversion
I’m sure I’ve never mentioned that I’m an amateur radio operator. Like Vegans and...
Advice I Like: Tipping
By Steve Jones
When in doubt, overtip – from Excellent Advice for Living This is close to...
Forums
How Much AI Code Would You Use?
Comments posted to this topic are about the item How Much AI Code Would...
Browsing for Instances
Comments posted to this topic are about the item Browsing for Instances
Creating a Date Dimension (Calendar Table) in SQL Server
Comments posted to this topic are about the item Creating a Date Dimension (Calendar...
Question of the Day
Browsing for Instances
I have a SQL Server instance that is not listening for connections on port 1433. By default, all ports are locked down on my server, except for the SQL Server port. What can I do to allow users to connect to the instance without knowing the port?
See possible answers