Get all user tables with size
Returns User Tables by SIZE in DESCENDING ORDERAdd TOP n clause in SELECT to get selective results (i.e. TOP 10 TABLES)
2006-01-25 (first published: 2003-06-07)
2,441 reads
Returns User Tables by SIZE in DESCENDING ORDERAdd TOP n clause in SELECT to get selective results (i.e. TOP 10 TABLES)
2006-01-25 (first published: 2003-06-07)
2,441 reads
This script kills all the user sessions except its own.This T-SQL block can be converted into a stored procedure by adding following lines in the begining of the script - Create Proc Kill_Sessions As
2003-06-18
2,741 reads
This script will search a specified string in the current database and return all the tables with their columns containing that string. SET @search_str variable with the string to be searched (max. length allowed = 1000 chrs)
2003-06-07
423 reads
By Chris Yates
AI is no longer a niche capability – it is a leadership catalyst. As...
By Steve Jones
A friend was asking for help with some data analysis. This was in PowerBI,...
I am responding late to a T-SQL Tuesday invite from John Sterrett. John’s call...
Comments posted to this topic are about the item How a Legacy Logic Choked...
Hi i was surprised to see the approach my coworkers used to sunset talend...
Comments posted to this topic are about the item People Make Odd Choices
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