I expect it does, as long as these backups are logged in MSDB.

Perhaps I did not explain my point clearly.

Your article suggests using the "ALTER DATABASE ... " T-SQL command to bring the database back online. This is, of course, fine....

Good article! One possible source of confusion: the screenshots showing 'completed with errors' and 'success' will not show after issuing the command "ALTER DATABASE [yourDB] SET ONLINE" but after performing...

post removed, hadn't seen it was solved..

I did, a while ago, on another topic (storing perfmon counters in a SQL central repository), but it was never picked up.

At least in this way I do not...

Not knowing enough about SSIS, I devised another solution in which a central (management) server retrieves SQL error logs from managed servers and stores them in a central repository.

It will...

Steve, I followed up on your suggestion. You will find the article (Storing multi-server Perfmon counters in a central SQL database) in the Contribution Center on the site.

Regards, Willem

There is another option: using a central management server for perfmon (perfmon can read counters from remote servers), and storing the perfmon values in a SQL database on the management...

Could it be your SQL server is running under a non-domain account (e.g. local system) and has no rights to access the UNC path?

My script (not yet tested on 2005!) assumes the secondary server is logshipping only, so sids can be kept identical

If not, and sids differ, you should map the db-user sid...

It may look somewhat confusing. Check out the explanation in BOL 2005 on 'Managing Batches for Bulk Import'. ROWS_PER_BATCH is a performance parameter, not a parameter that manages the batch...

Are you using SQL 2000? If so, I once created a SQL Agent job that does the trick, but I have not tested it on SQL 2005.

It is made up...

BOL 2000 says:

Using ROWS_PER_BATCH

If the -b switch or BATCHSIZE clause is not used, the entire file is sent to SQL Server and the bulk copy operation is treated as...

Michael,

ROWS_PER_BATCH is not the same as BATCHSIZE (check out BOL), and is only used for optimizing, not for transactional purposes. That may explain the behaviour you experience.

I use this type of script:

-- Find the latest backup

DECLARE   @lastbackupID int

        , @backupname   nvarchar(260)

        , @dbname       sysname

SET @dbname = '<dbname>'

SET @lastbackupID = (SELECT...