Hi, I dont think you can install SL 2005 enterprise edition in Windows Vista...enterprise edition is not supported in windows vista.refer the below link,

http://msdn2.microsoft.com/en-us/library/ms143506.aspx

you need to take a full backup and restore it using with standby option, remaining steps are fine........also you need to create a shared folder and give modify privilege for...

In the case of database mirroring once the principal failovers to mirror server you need to sync and recreate the logins by using SSIS to transfer the syslogins table and...

Sathya, you can refer the links which i had provided already.........i guess it wud be useful.Anyways even though you had manually deleted the jobs there would be entry for the...

refer these articles and revert if you need any help,

http://sql-articles.com/ 

http://sql-articles.com/articles/lship/lship.htm feel free to provide your comments if any

Well if your log shipping is out of sync first check the monitor server and find which T-log is missing or failed to restore /copy in the secondary server......the log...

refer, this http://deepakinsql.blogspot.com/2007/08/how-to-recover-from-suspect-database.html check if this helps

Chirag,

         if you had downloaded SP2 after March 05 2007 then everything is fine.....if you have the previous SP2 released b4 it you will face some issues with maintenace cleanup task...refer,...

i think even if you append it to a single file you can restore it by specifying each one individually as,

restore headeronly from disk='Path of your.bak file'

it will generate...

In simple recovery model you can take only full backups and log backups are not possible as it will truncate the log and issues checkpoint, if you use simple recovery...

Mark, Thanks for providing the solution for your problem....so that those who view this thread will be benifited...........

Try deleting the jobs and it will generate an error if any this time can you try it and get back to me

Mark, I had the same issue last week what i did was queried the sysmaintplan_subplans and removed the entry for the maintenance plan from this system table.......then it was once...

my advise is to go for SP2 as many problems faced in SP1 are fixed with Service pack2....backups schedule depends on your requirements, if your db is extremely critical and is...

I dont think Sp3 is available for SQL 2005 refer, http://support.microsoft.com/kb/913089 

for installing sql 2005 refer,http://dumthata.com/sqlchn/articles/install/insql.htm and also always have your data and log files in a separate drive...