I guess, Backup / Restore is the best bate here and you can also restore latest t-log to get data close to current.

To install sql server clustering you need OS clustering first and I doubt VISTA provide the same. you need a server.

.bak is like a snapshot of your current database whatever is there in your current database it will restore the same way.

Refer following link for more detail on sp_spaceused:

ms-help://MS.SQLCC.v10/MS.SQLSVR.v10.en/s10de_6tsql/html/c6253b48-29f5-4371-bfcd-3ef404060621.htm

Duplicate post. Avoid dupliation please.

Another scenario to shrink the log is when you don't have sufficient disk space and your log is abnormally huge. But it's not ideal to shrink log often.

If I am not wrong; upgradation can't be done from X86 to X64.

You can also execute following command to check Database version

select serverproperty ('ProductVersion')

You can also execute following command to check Database version

select serverproperty ('ProductVersion')

You can also execute following command to check Database version

select serverproperty ('ProductVersion')

Chek out if table partion can hlep in your scenario.

Chek out if table partion can hlep in your scenario.

You did get it. I want you to register the server first. And than connect.

Register the other network machine to the primary server; if successful. Do Logshipping through wizard.

Check you do have sufficient privilages to connect to the said server.

Surely you can put db in simple recovery mode and it will help but before changing recovery model make sure this database is not used into production.

If you will...