i'd start by running the 2005 upgrade advisor, also check out if you need to go up a service pack...

It will give you a place to start from.

Also it maybe...

I beleive but may be wrong that it represnts the datatype of the column in question.

35 = Text

99 = NText

Not sure this directly relating to your problem but it maybe a place to to start

http://support.microsoft.com/kb/323602

Out of curiosty what backup agent are you using?

If you access the job through EM and the agent you shouild be able to open the job, then right click and exeute the step in question.

have there been any addition SSIS/DTS Imports taken place, have you created/rebuilt any indexes. Does your db grow automtically? if so could the automatic expeansion have taiken this space... i.e....

If you use vbs you should use the active x script, i did have a script that did a similar thing but i have mis-placed it somewhere, if not google...

Assuming the continous connection does not have dbo user access, you could restrict access to the database only to dbo thus preventing connection....assuming you have dbo access, you can restore.

You could also script out the logins and users from the 2000 server and run the script on the 2005 instance.

so i fyou have written your own appication then you may want to encrypt your SP's etc so your customers cannot see the underlying code...

it probably will be slower accross the network.

If you restore is local, does the backup exist on the same drive as the database files. this can make restores perform poorly...

kaykay you proably need to be more specific if you want to get some meaningful answers.

Failover of log shipping is a manual process, MS have produced this article describing the process i hope it helps

http://msdn.microsoft.com/en-us/library/ms191233.aspx

I assume you have created the SSIS package for processing the cube...this article talks about scheduling SSIS packages...

http://www.codeproject.com/KB/aspnet/Schedule__Run__SSIS__DTS.aspx

Hope this helps

This link might help...

http://www.sql-server-performance.com/articles/clustering/cluster_sql_server_2005_p1.aspx

There are some settings in replication that keep the publisher and subscriber in sync. without going into too much detail check this li

http://technet.microsoft.com/en-us/library/aa237094(SQL.80).aspxnk out