List all primary keys
Thanks to Raul Sharma for his brilliant ideas. This is a modification of one of his scripts. The script takes only the user tables. Those tables which does not have PK are not listed!
2001-12-13
777 reads
Scripts
OSQL Process Watcher
These 2 files plus sleep.exe (Resource kit) gives an administrator a good view of important blocking statistics in almost a real time fashion. You can use this with profiler to obtain some unique information very fast on a lead blocker if your gathering the right counters in profiler and dumping them in a table and […]
2001-12-10
604 reads
Pass an Array into a Stored Procedure
Have you ever wished T-SQL allowed you to pass an array into a stored procedure? Well the spListToTable stored procedure listed below accepts a delimeted string and turns it into a table. Code your stored procedure to accept a varchar, create a temporary table, call spListToTable, and use the populated temporary table as if it […]
2001-12-10
2,908 reads
Fix - Orphaned User Connections
Run the '1'-first script.This stored procedures will easily script all the logins and passwords, which will then help you to transfer them to another SQL Server. Run the '2' - Second Script. This will fix the Orphane Connections. Run the '3' - Third Script. Fixing some Orphaned Users left after step 2. NOTE: Script below […]
2001-12-09
2,206 reads
How to Short-circuit Where Clauses
There are many times when you might be concatenating text in a stored procedure to make a where clause, because the input parameters are optional. An alternative is to create many versions of the stored procedure - one for each possible combination of parameters - which can soon become too big. There is a more […]
2001-11-25
4,323 reads
Loop through records without using a cursor
I sometimes have to loop through records in a database and perform a specific action on the value that is returned. For example, In the script below I loop through the user tables in sysobjects and simply print them out. This technique is useful when dropping all indices/triggers on a particular table, or adding WITH […]
2001-11-25
9,218 reads
Convert Hex value to Signed 32-bit int
Convert, up to 8 nibbles, hex string ('FFFFFFFF'...'00000000')to signed 32-bit int (-2147483648..2147483647).
2001-11-15
2,525 reads
Convert Hex value to Signed 64-bit bigint
Convert, up to 16 nibbles, hex ('FFFFFFFFFFFFFFFF'..'0000000000000000') to Signed 64-bit bigint (-9223372036854775808..9223372036854775807).
2001-11-15
711 reads
Dropping all Triggers
When implementing a pilot study of audit trail triggers, you often want a way of removing all triggers in the database in order to retest your scripts: here it is!
2001-11-08
1,631 reads
Another script from DOS but shows alerts
Like the one posted before, the use of the SP is like this: proc_alerts 1,18. This will show the first 18 alerts on the system. OR proc_alerts 20,35 will show from 20 to 35. This lets you manage the list without letting go out of the screen.
2001-11-03
1,243 reads
Blogs
The #MS_DatabaseConnector## Role: #SQLNewBlogger
By Steve Jones
I had seen these roles in various instances, but never dug into the new...
Asking for Help Isn’t a Weakness
By Brian Kelley
During COVID, I attended training on software/enterprise architecture given by Mark Richards. One of...
The Proof of the Backup Is in the Pudding
For me, the objective is straightforward: have a backup strategy that is reliable, understandable,...
Forums
Access + ODBC Driver 18 + SQL Server 2025: ~150–250 ms per request
Has anyone encountered recurring request latency when using Microsoft Access with SQL Server 2025...
The ##MS_DatabaseConnector## User
Comments posted to this topic are about the item The ##MS_DatabaseConnector## User
Planning for Change
Comments posted to this topic are about the item Planning for Change
Question of the Day
The ##MS_DatabaseConnector## User
On SQL Server 2025, I run this code as a sysadmin:
CREATE LOGIN Demo WITH PASSWORD = 'Demo1234567' GO ALTER SERVER ROLE ##MS_DatabaseConnector## ADD MEMBER Demo GOI then login as Demo and run this:
USE sandbox go SELECT CURRENT_USERWhat is returned? See possible answers