is a connectivity problem (could be anything)

- can you ping the sqlserver ?

- provide a correct userid and password for the connection.

- can you connect to the sqlserver using query...

check your stored proc "USR_Demographics" for string "g?tdate"

keep in mind that the function getdate() cannot be used as a default value of an input parameter for a stored procedure !

- end you statement with a semicolon ;

- this also can do the trick

alter TABLE [dbName].[dbo].[tableName]

add  colx bit not null default 0 ,

       coly bit not null default 0...

- maybe tablediff utility can do that for you. aarch that's sql2005

- I guess the SQL_Server_2000_Web_Services_Toolkit can do that to.

table caching is a dangerous thing to do ! because when you pinn a table, it will not be cached out ! Maybe your table grows beyond your expectations consuming...

Maybe DTS can do a better job for you.

In addition to Pam Abdulla's reply :

If you're updating a varchar-type column, it may be possible sql has to relocate your row to another page, maybe even perform some pagesplits...

just try to do an easy client install using a script when you have vs2005 installed with sqlexpress or when sqlexpress with its...

If this is a full load/refresh or your applications are offline during this load, you might want to disable your Non clustering indexes ( if your data is thrustworthy

If you have a clustering index defined for your table, when you prepare your data for load, sort it according to your defined clustering index !

This way you avoid page-splits...

If you change to simple, it will only keep info for the open transactions.

So if your load is in a single transaction, it will still grow to 95 Gb.

Can you...

I hope this is a singleshot or investigative query you want to run, because the querytype proposed later on is certainly _not_ a general practise advise !!

connect to your server...

Well ... handling these kind of problems is not easy .... that's one downside of working with linked servers.

Start sqlserver perfmon to captuer the...

regarding the sqlteam article (good).

there is a downside with using ##pivot.. ##meaning global temp tb.... global = everyone... so only one can use it at a certain time.

Maybe this can help out generating your script :

-- I did change to not include Primary Keys !!

-- You'll have to drop/create the PK-constraints if you want to...