to transfer users from one system to another I typically use sp_help_revlogin. There's a different sp for sql200 and sql2005 so make sure you download the proper one (Even...

good info on this problem here...

http://forums.oracle.com/forums/thread.jspa?threadID=337842&start=0&tstart=0

I had a similar problem. I was using the "oracle provider for OLE DB" driver. I switched the drivers to use the "Microsoft OLE DB provider for...

Are drive letters a factor here at all? In the past, I've been limited to 3 instances on each node (of a 2-cluster node). If you have a...

While placing the TemDB on a separate drive is a "best practice", it's not an automatic to do. It all depends on your application. Is your App doing...

generate a script from the backup file? not sure how to do that. The reason I want to do this in the first place is because I lost...

In cluster Admin take the SQL Server offline and add the disk drive as a dependency, bring back online.

the syntax I used was TCP://ipaddress:port

so, for example... TCP://10.10.10.10:1103

I've used the ip address (In plasce of the FQDN) in the gui and it worked just fine. might want to give that a try....

If you use method 2, the cluster will consider that a failure and attempt to fail it over. The only way to shut down an instance on a cluster...

hmmm, interesting idea. I'd be very interesteed to know how the startup script determines what side of the cluster it's on and whether or not another instance is already...

you need to set the "max server memory" in sp_configure for each side. You must account for a fail-over. If an instance on one side is already using...

I've also have used the exact Intel utility Michael suggest many times and it clearly lists the processors, cores and whether it is hyper threading or not. Very easy....

I've used a free download called DTS Backup 2000. You can get a copy here; http://www.sqldts.com/242.aspx

Possibly an orphaned sid problem. You may need to run the sp_change_users_login procedure to fix them after your retore.

syntax: sp_change_users_login 'auto_fix','userid'

to identify if you have an orphaned sid;

sp_change_users_login...