Viewing 15 posts - 136 through 150 (of 342 total)
>> 3.What above error means from SQL Server prospective?
That would mean that your database (ReportServer) is using the full or bulk-logged recovery models. This means that the transaction...
SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017.
June 20, 2010 at 1:40 am
Use DBCC CHECKDB. Preferably before the backup too. If after the restore, DBCC CHECKDB returns consistency errors, you can at least tell if the error was because the...
SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017.
June 9, 2009 at 12:38 am
Things you should be aware of re. RESTORE VERIFYONLY here.
Verifying SQL Server backup files on a file server on a budget here.
SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017.
June 9, 2009 at 12:21 am
Sr SQL developer (10/29/2008)
I was able to purchase 10 copies of SQL Backup Lite (without compression) for about the same price as 1 copy of LiteSpeed.
The Lite version does support...
SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017.
October 29, 2008 at 11:23 am
Art (10/22/2008)
Nobody has deleted any rows on msdb.
How can you tell for sure? In SQL Server 2005, there's a sp_delete_database_backuphistory stored procedure, that can be used to delete backup/restore history...
SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017.
October 23, 2008 at 10:13 am
SQLBOT (10/17/2008)
Here is what happens on a full database backup
1. lock database blocking all transactions
2. place a mark in the tran log
3. release the database lock
4. back up all data...
SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017.
October 23, 2008 at 8:05 am
... because you can restore an individual table without having to restore the entire Database
Restoring an invididual table from a backup may not always give you the same data...
SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017.
October 10, 2008 at 7:05 pm
If you made a backup in sql 2000 you cannot restore it on sql 2005...
Have you ever tried doing this for real, to validate that statement?
SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017.
October 10, 2008 at 7:01 pm
Is that still the case if doing a shrink of the log file with truncate_only, as the OP was doing?
Yes.
I would like to know what are the options I...
SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017.
October 9, 2008 at 4:33 am
Inserting dummy records is no longer necessary in SQL Server 2005, as shown in the example. SQL Server handles that for you when you attempt to shrink the log....
SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017.
October 8, 2008 at 10:50 am
I would suggest checking the permissions of the SQL Server service startup account against the folders where the database files are located, and the file permissions itself. The description...
SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017.
October 8, 2008 at 9:09 am
You can shrink a transaction log file only up to the boundary of a virtual log file. See this link for details.
SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017.
October 8, 2008 at 7:07 am
Our system has 20 inserts a second.
Your post suggests that your database is still active when the index rebuild is running. If so, you should also consider if you...
SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017.
September 23, 2008 at 8:51 pm
That would depend if you have ever performed a full backup of that database. If not, that database would behave as if it was running in the simple recovery...
SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017.
September 23, 2008 at 7:09 am
So the performance impact is most noticeable when your database is UPDATE/DELETE heavy, but not if its INSERT heavy.
SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017.
September 23, 2008 at 7:01 am
Viewing 15 posts - 136 through 150 (of 342 total)