Comments
Sort by recent activity
Nothing is highlighted as different between the two procs. / comments
Nothing is highlighted as different between the two procs.
Is there a debug mode or something that will create a log file? My boss is going to make me split the procs again... this is getting out of hand. / comments
Is there a debug mode or something that will create a log file? My boss is going to make me split the procs again... this is getting out of hand.
> Does this mean that the large sp's still state that they're different after synchronization?
Yes.
> What differences are being reported when the sp's get over 32K?
I think it just highlights the last line procedure, but there is no visible difference. I'll check with my boss who does the synch. / comments
> Does this mean that the large sp's still state that they're different after synchronization?
Yes.
> What differences are being reported when the sp's get over 32K?
I think it just highlights the ...
My production database needs big log files, which is fine. My read-only report database does not, especially since the logs are empty. I was just hoping there is a way to restore a database without the logs or with log files that were smaller than the original. I wonder if I can backup a database with "no_log", and then restore it with a "fake" empty log file that I create. / comments
My production database needs big log files, which is fine. My read-only report database does not, especially since the logs are empty. I was just hoping there is a way to restore a database witho...
petey wrote:
When you perform a full database backup, SQL Server will back up the active portion of the transaction log, which starts from the oldest active transaction.
If only the active portion of the transaction log is backed up, what does my restore operation take longer as the log grows? One of my databases is 170 GB, and its log file compresses to about 120 GB. After compression, it will grow as big as 250 GB before we compress it again. The bigger it gets, the longer the restore takes (up to twice as long). It seems like all the restore should be doing is creating an empty log file the same size as the original. / comments
petey wrote:
When you perform a full database backup, SQL Server will back up the active portion of the transaction log, which starts from the oldest active transaction.
If only the active por...
I have added this to my backup job for tonight.
If there is no active portion of the transaction log, will it restore with no log? The restore currently creates a log that is the exact same size as the original, so shrinking the log file before backup helps when I run out of disk space (the 400 GB I mentioned earlier is after shrinking). / comments
I have added this to my backup job for tonight.
If there is no active portion of the transaction log, will it restore with no log? The restore currently creates a log that is the exact same size a...
I'm still having the problem, and your post is pretty old. / comments
I'm still having the problem, and your post is pretty old.
I recently increased my compression level to 3 - so I will change it back to 2. This problem only occurred once. I have my job set to auto-retry and it worked the 2nd time. I'm running version 5.2.0.2825 and I'm using 7 threads for this backup. I notice the original poster is using 6 - maybe the number of threads used can increase the likelihood of this error occurring. The database is 241 GB and I'm running on a 64-bit server. I am running multiple backups simultaneously.
I hope this information can help you reproduce the bug. / comments
I recently increased my compression level to 3 - so I will change it back to 2. This problem only occurred once. I have my job set to auto-retry and it worked the 2nd time. I'm running version 5.2....
I had to update my service account login, and copy the ProductActivation.exe file to get it to work.
Thanks / comments
I had to update my service account login, and copy the ProductActivation.exe file to get it to work.
Thanks
I got it to work. I had to join in sys.indexes to get index name: SELECT name FROM master..sysdatabases WHERE dbid = 8
USE support
GO
SELECT
object_name(partitions.object_id) AS [Table],
indexes.name AS [Index]
FROM
sys.partitions AS partitions
INNER JOIN
sys.indexes AS indexes
ON partitions.object_id = indexes.object_id
WHERE
hobt_id = 72057618332712960
It would be cool if SQL Monitor would do this automatically.
Thanks / comments
I got it to work. I had to join in sys.indexes to get index name:SELECT name FROM master..sysdatabases WHERE dbid = 8
USE support
GO
SELECT
object_name(partitions.object_id) AS [Ta...