So I should probably create the indexes and have a job go out once a week or so and confirm that they are still there?

My main concern is to place some...

Have you tried using enterprise manager (while connected to that database) and gone to tools-->replication-->configure and confirmed that the database is definately not set for replication?

if you run  select * from sysarticles in that database do you get any rows?

sp_configure 'allow_updates',0

reconfigure with override

update sysobjects set replinfo = 0 where name = 'billable_transactions'

sp_configure 'allow_updates',1

reconfigure with override

you actually just needed to remove replication for that table but...

you ran...

 exec sp_dropsubscription @publication = '<publication>, @article = N'all', @subscriber = N'<subscriber server>', @destination_db =...

'fraid so...the best way is to script everything out to drop and create the replication, as well as the alter table alter column statement and run it. Once the script...

If your column has no data in it then you could drop it and add it again, otherwise you'll have to resnapshot.

You are probably attempting to backup the database to a dump device when this error occurs. Look in enterprise manager under Management-->Backup you will see a list of devices, this...

Having terminal services for remote administration is fine, that gives you a limit of 2 remote users. The performance problem is only really going to be a factor if you...

Are you running on different hardware than the original box? There could be an issue with controllers and the machine getting confused as to what disk is on what controller....

Did you start SQL in single user mode before attempting to restore msdb.

I would never install software over terminal services, however using it I have never experienced a problem. That includes all the usual SQL functionality like designing, executing DTS, managing server...

Check the registry for

Hkey_Local_Machine-->Software-->Microsoft-->MSSQLServer-->Setup and confirm the SQLDataRoot path and the SQLPath path.

Also check

Hkey_Local_Machine-->Software-->Microsoft-->Microsoft SQL Server-->80 and check the SharedCode key.

Here's the link... http://www.sqlteam.com/item.asp?ItemID=6002

Enterprise manager --> right click SA, go to properties, type the new password in the password box, hit ok, type the new pwd again.