Data Dictionary from within SQL Server 2000
Mindy explores the metadata stored in SQL 2000 to show you how to produce a simple and useful data dictionary!
2007-10-02 (first published: 2002-02-11)
36,368 reads
Mindy explores the metadata stored in SQL 2000 to show you how to produce a simple and useful data dictionary!
2007-10-02 (first published: 2002-02-11)
36,368 reads
This script creates a stored procedure that you can call to get the record count for every table in a particular database. It uses the sp_MSforeachtable system stored procedure and a temp table.
2002-02-25
663 reads
This script is very helpful for anyone trying to recreate particular SQL Server Database Versions for Testing. It allows you to automatically recompile any stored procedures or views saved with drop, create and permission statements. The scripts must all be sitting in one directory and end in the same extension. I have found this very […]
2002-02-25
699 reads
Designing your application so that Stored Procedures are the only database objects that are accessed is generally the best practice. Agree? Disagree? Read this article by guest columnist Mindy Curnutt to see what she thinks!
2001-08-01
12,789 reads
By Steve Jones
Superheroes and saints never make art. Only imperfect beings can make art because art...
One feature that I have been waiting for years! The new announcement around optimize...
Following on from my last post about Getting Started With KubeVirt & SQL Server,...
Comments posted to this topic are about the item The AI Bubble and the...
Hi, in a simple oledb source->derived column->oledb destination data flow, 2 of my...
hi, i noticed the sqlhealth extended event is on by default , and it...
I am currently working with Sql Server 2022 and AdventureWorks database. First of all, let's set the "Read Committed Snapshot" to ON:
use master; go alter database AdventureWorks set read_committed_snapshot on with no_wait; goThen, from Session 1, I execute the following code:
--Session 1 use AdventureWorks; go create table ##t1 (id int, f1 varchar(10)); go insert into ##t1 values (1, 'A');From another session, called Session 2, I open a transaction and execute the following update:
--Session 2 use AdventureWorks; go begin tran; update ##t1 set f1 = 'B' where id = 1;Now, going back to Session 1, what happens if I execute this statement?
--Session 1 select f1 from ##t1 where id = 1;See possible answers