Update: I have just got log shipping running between two standalone servers, no domain at all. SQL Server & Agent were configured to use local user accounts (different...

I remember doing something like this a few years ago. From memory, the only way around it is to loosen your share & NTFS permissions on the folder that...

Make sure the share you are dropping the transaction log backups to for the secondary server to grab is a clustered resource (which means it will need to be on...

OK, a new version. This has tidied up a couple of things that were annoying me.

I have also added the ability to perform FILE or FILEGROUP backups....

This is a known issue with MSDB - there are some indexes missing that would improve performance. There is an article in the forums somewhere (search for "large msdb"...

I don't know about scripts, but there are a few commands you can run that would return the information (just not necessarily in the format you want):

sp_helplogins

sp_helprotect

select * from master.sys.server_principals

select...

What exactly is this query? Those error messages will appear if you are creating a stored procedure that makes calls to other stored procedures that do not exist.

Have a search on this site for articles and search the forums. There have been several discussions on this sort of thing.

Here's a couple of articles to get you...

Another revision. SQL version checking (will only run on SQL 2000, 2005), better logging, additional options.

Set Database name to:

ALLSYS = backs up master, model, msdb

ALLUSER = backs up all...

Try using some of the dynamic management views and functions - they reside in the resource database. E.g., SELECT * FROM sys.dm_exec_sessions. Have a nosy in Books Online...

Here's a revised version of the script. Now handles long folder/file names, checks server version is 2000 or 2005.

Looks more or less OK, albeit incomplete. I've attached a sample ERRORLOG to show what to expect (from one of our test 2005 clusters).

Good idea or not, if you're not sure what you are doing you should test first rather than jump straight onto production. The real trick there is to realise...

Are you connecting to the SQL Server virtual name (being as it's a cluster)?

What credentials are you logging in to Windows with?

What credentials are you connecting to SQL with?

If you can get SQL Server running in single user mode, try running these commands:

[font="Courier New"] ALTER DATABASE mssqlsystemresource

MODIFY FILE (name = data,...