2007-04-30 (first published: 2007-04-03)
1,696 reads
2007-04-30 (first published: 2007-04-03)
1,696 reads
2007-04-27 (first published: 2007-04-03)
1,295 reads
Here's the scenario: 1. You have been given a script to run.2. You do not know the database name.3. You know which server.Substitute the word "TABLENAME" with the table name in the script and run in query analyzer. This query will check every database on the server and return the name of the database with […]
2007-04-26 (first published: 2007-04-04)
505 reads
Check Indexes on all databases and rebuild/reindex based on fragmentation
2007-04-25 (first published: 2007-04-05)
1,475 reads
2007-04-24 (first published: 2007-04-05)
473 reads
This script is basically a front-end for the sp_"scriptproc" stored procedures that ship with MSSQL. This will allow you to create ALL of your procs (INS, UPD and DEL) on the fly using the article name instead of having to first search for the article ID. It also uses sp_scriptdynamicupdproc where appropriate. This facilitates quick […]
2007-04-23 (first published: 2007-03-27)
1,762 reads
When a table is modified by changing the order of fields or changing field type or adjusting field sizes etc, some of the dependent views (or views on views on views :)) may become invalid as they store some metadata in order to run more efficiently. These views would need to be refreshed with new […]
2007-04-20 (first published: 2007-03-20)
2,093 reads
A quick little standalone script that tells you what process is blocking and what processes the blocking processing actually blocking.When running this script in QA, change your output to "Results in Text" ( CTRL-T ). Utilizes the blocking info in sp_who2 combined with dbcc inputbuffer and a little cursor to wrap it all up. Formatting […]
2007-04-19 (first published: 2007-03-20)
7,480 reads
The script details about the workaround for using Dynamic SQL inside T-SQL user defined functions. Basically, T-SQL doesn't allow developers to perform/write any actions/statments which would affect the database's state. As a key note factor for any migration process from oracle to sql server developers need to do a work around on using execute immediate(for […]
2007-04-18 (first published: 2007-03-27)
4,104 reads
spWhatsRunning does just that. It tells you exactly what is executing on your server. By combining the output of the sp_who and dbcc inputbuffer, this script will tell you exactly whats being executed. DBCC INPUTBUFFER will tell you the same thing, but by the time you get the spid, the offending process may be gone. […]
2007-04-17 (first published: 2007-03-20)
2,771 reads
I am excited to host T-SQL Tuesday for the first time. I want to...
By Steve Jones
Redgate had some Claude training recently, which I went through as my knowledge has...
By Steve Jones
gnossienne– n. the awareness that someone you’ve known for years still has a private...
Working with SQL Server can involve more than just writing queries. Understanding database design,...
Comments posted to this topic are about the item Measuring Productivity
Comments posted to this topic are about the item Importing Excel files into SQL...
I have 3 instances of a brand new long running query that are executing on a SQL Server 2025 instance. Query store is enabled. One of the queries is killed by the administrator, one is cancelled by the user. The other runs to completion. How many rows are in Query Store for this query?
See possible answers