There are times when you have mulitple job failures and need to find out in a quick way which jobs/steps failed and what their rerun statuses are. This script creates a stored procedure in the msdb db to help you find out the statuses of these jobs.
2004-10-12 (first published: 2004-07-21)
144 reads
As you know, relational databases are set-based and aren't particularly suited for row-at-a-time processing. However, in situations with heavily fragmented data (lots of gaps), you may find that row-based processing does better than set-based processing. Alexander Kozak demonstrates.
2004-10-12
1,833 reads
The SQL Server 2000 Report Pack for Financial Reporting is a set of six Microsoft SQL Server 2000 Reporting Services reports that work with a sample financial database called FinSampleDB.
With the Report Pack, you have the choice of using the sample reports either as-is or as templates for designing new reports using the SQL Server Reporting Services Report Designer.
2004-10-11
1,924 reads
The SQL Server 2000 Report Pack for Microsoft Exchange is a set of 13 Microsoft SQL Server 2000 Reporting Services reports that work with a Microsoft Exchange sample reporting database.
With the Report Pack, you have the choice of using the sample reports either as-is or as templates for designing new reports using the SQL Server Reporting Services Report Designer.
2004-10-08
1,858 reads
Based on a script from this site, which sets ownership of all objects to dbo, this modification of the original author's code simply adds user defined functions (UDF's). Script now includes tables, views, procs and functions.
2004-10-07 (first published: 2004-07-19)
214 reads
MAK examines how to save all of the DTS packages from SQL Server to a structured storage file automatically.
2004-10-07
2,334 reads
Delete all rows from all user tables. Create stored procedure and execute the procedure to get rid of all rows from all tables. This will not drop your tables. Be very careful what you wish for!
2004-10-06 (first published: 2004-01-20)
102 reads
This script displays all tables in a database that has identity columns.
2004-10-06
149 reads
This article contains guidelines compiled by examining the .NET implementations of shipping .NET applications and analyzing the common performance mistakes that we found. The guidelines discuss selecting .NET objects and methods, designing .NET applications, retrieving data, and updating data.
2004-10-06
3,043 reads
A simple script created to summarize locking by spid, by database, by type with more user friendly descriptions. You can also run for a specific spid. Hope it's useful.
2004-10-05 (first published: 2004-01-27)
488 reads
I am responding late to a T-SQL Tuesday invite from John Sterrett. John’s call...
It’s been forgotten about and neglected for few years but I’ve decided to dust...
I am honored to announce that I have been renewed as a Microsoft MVP...
Comments posted to this topic are about the item How a Legacy Logic Choked...
Comments posted to this topic are about the item SQL Server 2022 Clusterless Distributed...
Comments posted to this topic are about the item Navigating Multi Platform Realities in...
For the Question of the day, I am going to go deep, but try to be more clear, as I feel like I didn't give enough info last time, leading folks to guess the wrong answer... :) For today's question: You’re troubleshooting a performance issue on a critical stored procedure. You notice that a previously efficient query now performs a full table scan instead of an index seek. Upon investigating, you find that an NVARCHAR parameter is being compared to a VARCHAR column in the WHERE clause. What is the most likely cause of the query plan regression?
See possible answers