2006-01-23
1,207 reads
Replication
2005-09-30
1,281 reads
Adventures in Replication
SQL Server 2000 replication is the easiest so far to setup and work with. However there are some areas that you can get yourself into trouble with if you are not careful. New author Chris Rock brings us a few lessons learned in getting replication working with a remote office.
2005-08-22
9,743 reads
Disable foreign keys
Ever need to disable some foreign key during the load of new data in some tables? (Eq: for a snapshot). The following just does that using a parameter (0 for disable and 1 for enable)
2005-08-15 (first published: 2005-08-05)
1,256 reads
Replication PreScreen for proper Primary Keys
THIS TABLE WILL HODL YOUR TABLENAME AND UP TO THREE KEY COLUMNS FOR CREATING YOUR PRIMARY KEYSTHE OTHER COLUMNS ARE USED IN PROCESSING THE KEY'S AND GENERATING THE ALTER TABLE ASTATEMENTS TOCREATE THE PRIMARY KEYS FOR YOUR DB. THIS TOOL IS HANDY FOR PREPPING FOR A REPLICATION STRATEGY TO HELP YOU QUICKLY INDENTIFY IF YOU […]
2005-08-03 (first published: 2005-08-01)
377 reads
usp_ToggleDatabases
usp_ToggleDatabases is a simple procedure that will switch the names of two databases.One of the main problems with using sp_renamedb to switch databases is that the procedure will wait until the database is free before the rename can be completed. If the new live database is also in use then there is a likelyhood that […]
2005-08-04 (first published: 2005-07-28)
493 reads
The identity crisis in replication
This article discusses three common problems DBAs are likely to encounter when columns have the identity property, which is defined as an attribute of int, smallint, bigint, decimal, numeric or tinyint columns that will auto-increment their value when data is inserted. These problems are humorously referred to as the identity crisis.
2005-07-28
3,765 reads
LOG SHIPPING FROM SCRATCH
We were experiencing significant issues with Cross Domain Log Shipping, even after getting help from Microsoft. The main reason was that in SQL Server 2000 you cannot access the Log Shipping Wizard from a scripting interface. This set of stored Procedures is all you need to setup a good log shipping framework in your organization […]
2005-08-01 (first published: 2005-07-18)
3,027 reads
Drop and Add Foreign Keys
Have you tried using DTS to load a database and those pesky foreign keys mess you up? This is actually two scripts, one to generate the SQL needed to drop all the Foreign Keys in a database and another to Add the Foreign Keys back when you are done. I've thrown in Disabling and Enabling […]
2005-07-13 (first published: 2005-06-22)
3,067 reads
2005-04-11
1,365 reads
Blogs
Advice I Like: Art
By Steve Jones
Superheroes and saints never make art. Only imperfect beings can make art because art...
Why Optimize CPU for RDS SQL Server is a game changer
One feature that I have been waiting for years! The new announcement around optimize...
Performance tuning KubeVirt for SQL Server
Following on from my last post about Getting Started With KubeVirt & SQL Server,...
Forums
The AI Bubble and the Weak Foundation Beam
Comments posted to this topic are about the item The AI Bubble and the...
data type gets lost in data flow
Hi, in a simple oledb source->derived column->oledb destination data flow, 2 of my...
i noticed the sqlhealth extende event is on by default , so can i reduce
hi, i noticed the sqlhealth extended event is on by default , and it...
Question of the Day
The Read Committed Snapshot Isolation behaviour
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