How can we help you today? How can we help you today?
eilandd
Activity overview Badges (0) Posts (13) Comments (18)

Comments

Sort by recent activity
Sorry for the delayed response. The query returns the appropriate results, no errors. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Warning 167
Sorry for the delayed response. The query returns the appropriate results, no errors.
0 votes
Peter; Thanks for your reply. It seems that time has healed this issue. We are no longer receiving the 913 error. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Warning 167
Peter; Thanks for your reply. It seems that time has healed this issue. We are no longer receiving the 913 error.
0 votes
It appears that the RedGate backups are actually working. However, they are being reported as failed. My suspicion is that the RedGate backup history is the culprit. Is it possible to clear the RedGate backup history for a single database? / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Warning 167
It appears that the RedGate backups are actually working. However, they are being reported as failed. My suspicion is that the RedGate backup history is the culprit. Is it possible to clear the R...
0 votes
After looking into this further we found that the error is related to DCOM. This is a PCI issue since it is required that DCOM be disabled. Can you supply manual upgrade proceedures that do not require DCOM? Thanks. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Access Denied error while upgrading MSCS cluster from 4.6 to
After looking into this further we found that the error is related to DCOM. This is a PCI issue since it is required that DCOM be disabled. Can you supply manual upgrade proceedures that do not r...
0 votes
Thanks for the help. The update has been applied successfully. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Access Denied error while upgrading MSCS cluster from 4.6 to
Thanks for the help. The update has been applied successfully.
0 votes
This happens occasionally; not every time but enough to be worrysome. We'll check the AV and we're also looking at the tape backup process. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Restore log shows file error after restore
This happens occasionally; not every time but enough to be worrysome. We'll check the AV and we're also looking at the tape backup process.
0 votes
Peter; Here's the sanitized log: SQL Backup log file 5/21/2007 2:45:15 AM: Restoring Target_DB (database) from: \\Source_Server\sqlbackup\Source_DB\Source_DB_FULL_20070521_0115.sqb 5/21/2007 2:45:15 AM: RESTORE DATABASE [Target_DB] FROM DISK = '\\Source_Server\sqlbackup\Source_DB\Source_DB_FULL_20070521_0115.sqb' WITH RECOVERY, MOVE 'DB_Data' TO 'g:\sqldata\Target_DB_Data.mdf', MOVE 'Other_Data' TO 'g:\sqldata\Target_DB_Other_Data.ndf', MOVE 'Consultant_Data' TO 'g:\sqldata\Target_DB_Consultant_data.NDF', MOVE 'Consultant_Data2' TO 'g:\sqldata\Target_DB_Consultant_Data2.ndf', MOVE 'Sales_Data1' TO 'g:\sqldata\Target_DB_Sales_Data.NDF', MOVE 'Sales_Data2' TO 'g:\sqldata\Target_DB_Sales_Data2.NDF', MOVE 'Sales_Index' TO 'g:\sqldata\Target_DB_Sales_Index.NDF', MOVE 'Consultant_Index2' TO 'g:\sqldata\Target_DB_Consultant_Index2.NDF', MOVE 'Consultant_Index' TO 'g:\sqldata\Target_DB_Consultant_Index.NDF', MOVE 'Operations_Data1' TO 'g:\sqldata\Target_DB_Operations_Data.NDF', MOVE 'Operations_Data2' TO 'g:\sqldata\Target_DB_Operations_Data2.NDF', MOVE 'Operations_Index' TO 'g:\sqldata\Target_DB_Operations_Index.NDF', MOVE 'DB_Log' TO 'g:\sqldata\Target_DB_Log.LDF', REPLACE Processed 2960 pages for database 'Target_DB', file 'DB_Data' on file 1. Processed 64 pages for database 'Target_DB', file 'Other_Data' on file 1. Processed 306232 pages for database 'Target_DB', file 'Consultant_Data' on file 1. Processed 310592 pages for database 'Target_DB', file 'Consultant_Data2' on file 1. Processed 89584 pages for database 'Target_DB', file 'Sales_Data1' on file 1. Processed 115024 pages for database 'Target_DB', file 'Sales_Data2' on file 1. Processed 89720 pages for database 'Target_DB', file 'Sales_Index' on file 1. Processed 224136 pages for database 'Target_DB', file 'Consultant_Index2' on file 1. Processed 223480 pages for database 'Target_DB', file 'Consultant_Index' on file 1. Processed 703640 pages for database 'Target_DB', file 'Operations_Data1' on file 1. Processed 700712 pages for database 'Target_DB', file 'Operations_Data2' on file 1. Processed 131824 pages for database 'Target_DB', file 'Operations_Index' on file 1. Processed 65 pages for database 'Target_DB', file 'DB_Log' on file 1. RESTORE DATABASE successfully processed 2898033 pages in 2395.222 seconds (9.911 MB/sec). 5/21/2007 3:25:55 AM: Error: Cannot open file "\\Source_Server\sqlbackup\Source_DB\Source_DB_FULL_20070521_0115.sqb". The process cannot access the file because it is being used by another process. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Restore log shows file error after restore
Peter; Here's the sanitized log: SQL Backup log file 5/21/2007 2:45:15 AM: Restoring Target_DB (database) from: \\Source_Server\sqlbackup\Source_DB\Source_DB_FULL_20070521_0115.sqb 5/21/2007 2:45:1...
0 votes
Thanks for the response. The situation is an automated creation of a reporting copy of a database. The reporting copy is on a different server so, yes, the MOVETO option is being used. But this is not a log shipping scenario. It is a full database restore, no diffs or logs. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Restore log shows file error after restore
Thanks for the response. The situation is an automated creation of a reporting copy of a database. The reporting copy is on a different server so, yes, the MOVETO option is being used. But this i...
0 votes
I'll add my issue to this one as well, even though there is another ticket for it (reference SRP-3585). We are constantly seeing the monitoring stopped error and it is always an insufficient privileges error on the HKEY_PERFORMANCE_DATA hive. We have 2 instances that consistently give this error, though all of our instances report it from time to time with no actual outage. One of the trouble instances is an active\passive cluster. The error is never reported for both nodes at the same time and is generally the passive node. For the most part the errors correct themselves and then reoccur. / comments
  1. Community
  2. SQL Monitor Previous Versions
  3. Monitoring error - too sensitive?
I'll add my issue to this one as well, even though there is another ticket for it (reference SRP-3585). We are constantly seeing the monitoring stopped error and it is always an insufficient privi...
0 votes
I see this as well and reported it earlier, (reference SRP-3585). My cluster is Windows 2008 R2 with SQL Server 2005. / comments
  1. Community
  2. SQL Monitor Previous Versions
  3. Lots of Monitoring Errors on a Clustered Service
I see this as well and reported it earlier, (reference SRP-3585). My cluster is Windows 2008 R2 with SQL Server 2005.
0 votes
Total activity
40
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
9