Merge replication is probably not used as often as it could be, mainly because of the potential complexities of this tool. New author Satia Madimchetty brings us a great article that simplifies one part of this SQL Server feature, the conflict resolution issues.
2006-02-13
14,127 reads
Replication is a great tool, but it has a number of restrictions on what you can do with replicated databases. Typically you cannot easily move a replicated database, but our own Andy Warren brings us a technique that can get around this.
2006-02-01
15,100 reads
2006-01-23
1,213 reads
2005-09-30
1,293 reads
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,780 reads
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,294 reads
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)
404 reads
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)
533 reads
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
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,069 reads
By Steve Jones
semaphorism – n. a conversational hint that you have something personal to say on...
This week I was at PASS Data Community Summit in Seattle, and I attended...
By James Serra
(This is the third post in a three-part series on how AI is changing...
Comments posted to this topic are about the item Pay for Performance, which is...
Comments posted to this topic are about the item Helping an English Student with...
I have a table, dbo.bittest, where I am testing an application response. This has this structure:
CREATE TABLE [dbo].[BitTest] ( [insertdate] [datetime] NULL CONSTRAINT [DF__BitTest__insertd__300F11AC] DEFAULT (getdate()), [a] [bit] NULL ) ON [PRIMARY] GOMy application runs this code:
INSERT dbo.BitTest
(
insertdate,
a
)
VALUES
(DEFAULT, 'true')
GO
See possible answers