Are you trying to restore the master database? You can only restore the master database if it is the exact same build level (source and destination).

Absolutely,

Imceda just released a product called SQL Watch. This product allows you to schedule a job to run (at any schedule you wish) and the job will alert any...

This database was backed up to a striped backup set containing two files. When restoring the database you must provide both files of the stripe in order to restore.

RESTORE...

Be wary of column level encryption. It sounds like a great idea but is miserable on performance. I also know that it is very difficult and potentially impossible...

the HTML parser twisted the stored proc a little. From BOL:

EXEC sp_attach_db @dbname = N'pubs',

@filename1 = N'c:\Program Files\Microsoft SQL Server\MSSQL\Data\pubs.mdf',

@filename2 =...

You can either use this stored proc:

-- =============================================

-- Attach database via sp_attach_db

-- =============================================

EXECUTE sp_attach_db @dbname = N'',

@filename1 =...

This is typically due to either a corrupted backup file or some bad hardware that the backup file sits on. Try and move the backup file to a different...

The amount of time required for a restore is very heavily dependent on several factors.

The hardware that your backup file sits on.

The hardware that your data files sit on.

If you...

There is no size limitation to the size of database that LiteSpeed can compress.  I've seen LiteSpeed run on databases greater than 5 TeraBytes and it has performed very well. ...

If you want to be super secure you should consider having an off site disaster recovery box. Consider a strategy like log shipping in order to keep an off...

Running a profiler trace has a significant performance impact on the server so I would not recommend using it as an auditing solution. As for daily tasks, I recommend...

good post!!

Give Speed Change Manager a shot from Imceda (www.imceda.com)

The way that differential backups are handled is as follows. SQL Server databases are broken up into pages, this way pages can be moved into memory for quick accessing....

What version of LiteSpeed are you using?

Did you backup to a network or local drive?

Have you moved the file across a network at all?

I've seen this error before when copying...