what is the recovery model of your "model" database?

If its full, change it to simple recovery as there is no use of putting "model" database in full-recovery untill you...

And a little bit more here :-

http://www.mssqltips.com/sqlservertip/2142/retrieving-sql-server-permissions-for-disaster-recovery/?utm_source=dailynewsletter&utm_medium=email&utm_content=headline&utm_campaign=2011127

Consider this scenarios, If employee 'a'...

To protect your database, SQL Server gives you the option by giving permission at login level.

Dont give access to any login with whom you don't want to share the database....

Script is good if we have all the required logins in place else we still need to create the logins first.

Also sp_change_users_login, report only about the orphaned sql login not...

Thanks for response and looking into this post.

Fortunately the system get recoevered and all files are healthy.

The problem was at OS level which get repaired without fresh OS...

your litespeed backup script will be something like :-

exec master.dbo.xp_backup_database @database = N'dbname', @filename = N'your backup file location\backupfilename', @with = N'STATS = 10'

Try to run this and please check...

Seems like the backup was taken by litespeed and during the backup job, there was some problem of disk/network failure.

Can you run the job again by first looking everything in...

Need to install on all nodes but at the time of registration just mention the server which you are using as of now.

But you said the you can see the data if you attach the driver to another VM? So if you can see the data you could in theory copy...

Do you intend to continue using the existing VM and is there space for the mdf's?

If so, you should be able to copy them locally and detach/attach the database again...

Easiest :-

Create a group and give required permission.

Add users A,B..............................Z to this group.

Easy to manage, Easy to configure security, easy to remove.

1) Are you sure there is no physical(disk/network) problem in placing the log file?

2) Have you tried differential backup? Are you getting the same error?

Probable solution for your problem :-

Take...

from cmd prompt, try this :-

sqlcmd -L >c:\serverlist.txt

which will search all the sql server in domain and will write it in c:\sqlserver.txt. You can later on open this file to...

If your database is already f...d, then you can simply create the new database with the backup/s you have.

If you database is alive and need to be refreshed with backup/s...