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)
117 reads
This script displays all tables in a database that has identity columns.
2004-10-06
154 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)
502 reads
Quick way to counts rows in all tables in a database without using Count(*).
2004-10-04
139 reads
Returns the number of records within a table without having to perform COUNT.
2004-10-04 (first published: 2004-02-03)
864 reads
This procedure returns the job history for any jobs run on a given day. The parameter should be entered in mm/dd/yyyy format surrounded by single quotes. I use it to produce a report of any jobs that failed on any given day.It should be created on the MSDB database.Example: EXEC usp_job_history '10/02/2004' This is my […]
2004-10-04
2,205 reads
SQL SCRIPT to grant DBC_Execute to all user defined Stored Procs.This SQL SCRIPT is handy specially after Stored Procs are DROPPED & CREATED; often users dont mention the SQL to grant DBC_Execute permission to the Store Procs.This SQL SCRIPT will grant execute permission to DBC_Execute for all user defined Stored Procs. The SCRIPT can be […]
2004-10-03
197 reads
2004-10-01 (first published: 2004-02-16)
145 reads
This is a script you can run on a per-server basis, from any database in Query Analyzer or incorporate into a stored procedure, that will examine all databases on that instance of SQL and show what Maintenance Plan(s) they are part of, if any. Shows clearly any databases that are not currently part of a […]
2004-10-01
550 reads
This is a UDF that counts the days between two dates ignoring weekends and corporate holidays (as supplied in a lookup table). This ignores the time component but could be adjusted should you need to. If both days are on the same work day then the elapsed days is considered 1. If started Monday and […]
2004-09-30
451 reads
By James Serra
Most enterprise questions do not live neatly in one place. The numbers may be...
Redshift keeps its SYS_* monitoring views for seven days in cluster, which is fine...
By Steve Jones
I was updating my session for the Data API Builder (DAB) recently, mostly to...
Telp/Wa 62 8218200233 PQHX+93W, Jl. RS. Fatmawati Raya No.6 A, RT.1/RW.5, Cipete Sel., Kec....
Telp/Wa 62 8218200203 Gedung Gajah Tebet, Jl. Dr. Saharjo No.Raya 111 Unit N &...
Telp/Wa:62 8218200174 Jl. Tebet Barat IX No.40, RT.6/RW.4, Tebet Bar., Kec. Tebet, Kota Jakarta...
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