becareful!

if you have triggers or indexes those will not carry over with the above script. If you don't then consider yourself a happy camper

I have see that happen in the "new" MS wireless Keyboards when the "FLOCK" key is not in the right state.

hth

Because without knowing exactly which values are going to be passed to avariable the execution plan may be suboptimal.

you can encapsulate the logic on a sp and use the new...

>>I was hoping for a tool that would drop constraints, move data and rebuild constraints. Sounds like a niche market for a new third party tool.<<

BULK INSERT can bypass the...

I don't think it Impersonates the Account going out of SQL Server it does impersonates the credentials for local SQL Server objects.

From BOL:

The Windows process spawned by xp_cmdshell has the...

If minimizing disruption means "0" downtime you need to add a second transaction log file on the "other" drive. Then mark the first one as fixed length and shrink it...

Well, statistics of a database is a very wide term. Can you be more specific ?

That error is because you are probably connected to a database that has compatibility level set to 8.0 (2000) instead of 9.0 (2005)

Cheers,

...

... and she *strikes back* with elegant writing and a very nice must-read article

Once again I have to opose to the

IF not exists()

Insert ...

Technique. That statement does *not* guarranties that after two connections return from the "If" part with the same...

TVQuery maybe a Table Variable Query ?

Like:

declare @t table (x int )

select * from @T

Which by the way does not participates in transactions !?!

you have millions of rows per day, but does that justify one table per day ?

to answer your question

create several varchar(4000) and concat them in a dynamic exec like

exec...

When using Views and a linked server, the metadata has to be passed around. If there is a problem with that you get hanged.

Does a simple select in the...

Definitely is an architectural issue to keep replication at that pace but it is not strange to me. First separate the distribution database into its own server and secondly change...

Have you rebooted both ?