To my uinderstanding i dont think its possible, though a workaround solution if u like

in delete procedure put a command to move records to a new archive database and then...

There is nothing like deactivate...disableactually delete all configuration done

if you really wanna deactivate then stop replication agents.

there is no one line command which delete whole configuration though from GUI you...

open ssms >> add sql 2000 server there >> open sql 200 server and open publisher /distributor / subscription properties there in security tab use proper sql authentication to to...

in distribution database table name is something llike mssubscriber_agent and mssnapshot_agent....all info is there just need to search sysobjects

snapshot & distribution agent accept a parameter which define how many threads would be used for syncronisation, more threads more fast data transfer....use default setting with this change and see,...

if you have already subscribe article and article have data dropping procedure and creating it again with commented code will work...remember to drop and create do not "modify".....it will work...

Jason,

Here's the list of questions you need to answer for us to help u better...

how many total databases u have except system db's

Whats there total size used and empty space...

idea of modify default file group seems best for your criteria....though id the idea is just to move this table to another filegroup then recreating clustered index provide method to...

i know sp_refreshview is the method though though alter view might be new one thus that selected....had the answer option was "exec sp_refreshview N'myView'" i would have definately selected that...

With 3 nodes you are going for sql enterprise edition thus go for quad core processors as to save license cost, and quad cores allow more room for upgrade in...

i think you are using some extended dll thus it get locked...there is a dbcc command to free dll, i dont remember on top of my hand but you can...

if you are using sql 2005 u r in luck....it maintains the versions...

try this command and you can see how many times a procedure created...

select * from syscomments c,...

Transaction log might got filled if there is any open transaction remains...if you are able to truncate the log then this is not the issue...

Looks like its some job you...

if you are using local logins you need to use a trick...cause you cannot add sql 2005 as distributor to sql 2000 management studio, so to verify authentication settings are...

limitation is you can't concatinate 2 variables in a dbcc command.....

concatinate them before in another variable and then just pass that variable....

set @test-2 = @tableschema + '.' + @tablename