DR = Disaster Recovery.

a SQL disaster Recovery Regime would simply be the steps you plan to take to bring SQL server back up in the event of a disaster...whether that...

yes! that is the "tipping point" Jeff was referring to; most huge updates take seconds/under a minute total, isntead of hours.

after your update, have you done a select to...

i agree with Bru; i don't think you can change column names via replication.

an alternative might be to create a view that aliases the column names, but if these are...

not that a million records a day is a lot, but here's a question for you:

are the million records at a time date related? ie since you are doing this...

the error pretty much tells you what the issue is.

when you do a CREATE TABLE statment, you can optionally say what filegroup it will be created on...the "default" group is...

i'd say there was an error in assigning roles;

how can you update something(db_datawriter) if you can never query it for the original values(db_datareader)

i think you need to add db_datareader to...

here's my guess at it:

DECLARE @pid int

--don't see it assigned a value..this might be a select for ALL recs, and pid is the current record?

SELECT ISNULL(CustName,'') As CustName,

ISNULL(CustAddress,'') As CustAddress

FROM...

yes, you could use a loop from one to twenty or something, so it only iterates thru ranges of id's; you were right, the idea is to not let it...

you'd simply change your update statement just a little bit, so it only updates where the destination column is null;

something like this:

SET ROWCOUNT 500000 --only fiddle with half a million...

a default, any default constraint in fact, uses the value ONLY if the column is not referenced in the INSERT statement. the empty string you included gets assumed to be...

Seth you could give LINQPad a try, since it is free;

I like it because i can carry it in a thumb drive; added it to my PortableApps collection;

it's got a...

the default trace is helpful for this exact sort of thing, as it captures all the DDL changes

there's even a built in report for it.

go to Object explorer in SSMS,...

yeah you'd want to add something like WHERE dbo.CHARINDEX2('-', COLUMNNAME, 2) > 0

to your query, so you only select things that match the style of two dashes to chop...

seems like this function would help you here from the scripts contribution section:

http://www.sqlservercentral.com/scripts/30497/

it lets you find the N-th occurrance of the dash for example...

so if you need everything LEFT of...

here's a quickie SQL to find tables with "gaps" in the column_id sequence:

select distinct object_name(object_id) As TableWithGaps

from (

select * ,

...