How can we help you today? How can we help you today?
Eddie D
Activity overview Badges (0) Posts (38) Comments (1667)

Comments

Sort by recent activity
Thank you for your post into the forum. Unfortunately there is not an option available within SQL Compare to Ignore the 'WITH ENCRYPTION' syntax when comparing or synchronizing database objects. Also I am unaware of a work around for the problem you have reported to us. I have added the details of this forum post to an existing Feature Request, requesting to add an Ignore WITH Encryption option. The reference number for this request is SC-4419. At this time the feature request is marked for review. Hopefully the requested feature will appear in a future version of SQL Compare. Many Thanks Eddie / comments
  1. Community
  2. SQL Compare Previous Versions
  3. How to ignore the 'WITH ENCRYPTION' phrase ?
Thank you for your post into the forum. Unfortunately there is not an option available within SQL Compare to Ignore the 'WITH ENCRYPTION' syntax when comparing or synchronizing database objects. Al...
0 votes
Thank you for your reply. Sorry that SQL Backup did not help you move this database to a new server. Please do contact us if you encounter a problem in the future: E-mail - support@red-gate.com Telephone: US and Canada - Toll free 1 866 997 0378 UK - 0870 160 0037 Rest of the World +44 870 160 0037 Many Thanks Eddie / comments
  1. Community
  2. SQL Backup Previous Versions
  3. SQL Backup 6 restore error
Thank you for your reply. Sorry that SQL Backup did not help you move this database to a new server. Please do contact us if you encounter a problem in the future: E-mail - support@red-gate.com Tel...
0 votes
Hi Brad Sorry that this error is occurring. I see that you are attempting to restore from a local disk ('f:\lonas18_RiskModels_FULL.sqb' ). Was the backup file copied from a another location to the local drive outside of SQL Backup, using Windows Explorer for example? If the answer is yes, I have known for this process to corrupt the copied backup file. You can check for this condition using a hash generator, if the check sum generated is different between the original file and the copied file, I suspect that the copied file has corrupted You can download a simple hash generator using this LINK. Alternatively, are you able to copy the backup file to another local disk and attempt the restore from that location? This part of the error message indicates that the error maybe a system error: SQL error 3271: SQL error 3271: A nonrecoverable I/O error occurred on file "???:" 1117(error not found). Are there any entries in the event viewer log files at the same or similar time to the failed restore attempt? Do you get similar error messages using native Microsoft SQL Server Backup to perfrom both the backup and restore task? Many Thanks Eddie / comments
  1. Community
  2. SQL Backup Previous Versions
  3. SQL Backup 6 restore error
Hi Brad Sorry that this error is occurring. I see that you are attempting to restore from a local disk ('f:\lonas18_RiskModels_FULL.sqb' ). Was the backup file copied from a another location to th...
0 votes
The problem is due to SQL Server not releasing the xp_sqlbackup.dll file for upgrade. As part of the upgrade process we issue DBCC xp_sqlbackup(FREE) to get SQL Server to release our dll file for upgrade. However SQL Server does not release the file and we have never been able to accurately identify the cause. In some cases, retrying the upgrade process resolves the problem. Another way of loading the new or upgrade dll file is to perform the following: DBCC xp_sqlbackup(FREE) EXEC sp_dropextendedproc sqlbackup EXEC sp_dropextendedproc sqbstatus EXEC sp_dropextendedproc sqbutility EXEC sp_dropextendedproc sqbmemory EXEC sp_dropextendedproc sqbdata EXEC sp_dropextendedproc sqbdir EXEC sp_dropextendedproc sqbtest EXEC sp_dropextendedproc sqbtestcancel EXEC sp_dropextendedproc sqbteststatus Stop the SQL Server Service. Find all previous versions of xp_sqlbackup on your system and remove them including the installation folder. Find the new version of xp_sqlbackup.dll ( a copy can be found in the SQL Backup GUI installation folder) and copy this to the SQL Server instance BINN folder. Start the SQL Server Service. sp_addextendedproc sqlbackup, “xp_sqlbackup.dll†sp_addextendedproc sqbstatus, “xp_sqlbackup.dll†sp_addextendedproc sqbutility, “xp_sqlbackup.dll†sp_addextendedproc sqbmemory, “xp_sqlbackup.dll†sp_addextendedproc sqbdata, “xp_sqlbackup.dll†sp_addextendedproc sqbdir, “xp_sqlbackup.dll†sp_addextendedproc sqbtest, “xp_sqlbackup.dll†sp_addextendedproc sqbtestcancel, “xp_sqlbackup.dll†sp_addextendedproc sqbteststatus, “xp_sqlbackup.dll†Many Thanks Eddie / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Upgrade fails on Repository server
The problem is due to SQL Server not releasing the xp_sqlbackup.dll file for upgrade. As part of the upgrade process we issue DBCC xp_sqlbackup(FREE) to get SQL Server to release our dll f...
0 votes
Thank you for your post into the forum. When executing a synchronization script created by the SQL Compare (or SQL Data Compare or using the Comparison SDK), it may be desired that some ad-hoc queries be intermixed with the SQL produced by the Red Gate APIs. Because the BlockExecutor class can only run SQL code by converting ExecutionBlocks to SQL code and submitting them to the SQL Server, custom SQL cannot be introduced into the query stream. It is possible, however, to break an ExecutionBlock into individual query batches and running them using the .NET Framework's ADO .NET methods. In the following C# example, first, a connection is made to the server using the connection properties of the second database. Then a transaction is created. The custom SQL query is run first, then each batch of SQL from the ExecutionBlock in order. Finally, the transaction is committed. If any errors occur during the execution of the SQL script, then the error is written to the console and the transaction will be rolled back. ExecutionBlock block = provider.GetMigrationSQL(session, new SelectionDelegate(this.SyncRecord), true); ... System.Data.SqlClient.SqlTransaction trans = null; try { // Make a connection string from the second database connection properties System.Data.SqlClient.SqlConnection conn = new System.Data.SqlClient.SqlConnection("Data Source="+db2.ConnectionProperties.ServerName+";Initial Catalog="+db2.ConnectionProperties.DatabaseName+";Integrated Security=SSPI"); System.Data.SqlClient.SqlCommand cmd = conn.CreateCommand(); conn.Open(); trans = conn.BeginTransaction("MyTransaction"); //Run batches for (int i = 0; i < block.BatchCount; i++) { Batch b = block.GetBatch(i); if (!b.Marker) { cmd.CommandText = b.Contents; cmd.ExecuteNonQuery(); } } trans.Commit(); } catch (System.Data.SqlClient.SqlException se) { Console.WriteLine("Execute SQL failed: " + se.Message); trans.Rollback(); } I hope the above helps in resolving your issue. Many Thanks Eddie / comments
  1. Community
  2. SQL Compare Previous Versions
  3. Execute synchronization SCRIPT via .net sqlClient.SqlCOmmand
Thank you for your post into the forum. When executing a synchronization script created by the SQL Compare (or SQL Data Compare or using the Comparison SDK), it may be desired that some ad-hoc quer...
0 votes
Thank you for your reply. I have now submitted the feature request for the SQL Backup Development Team to consider support for HP Polyserve and Neverfail clustering solutions. The reference for this feature request is SC-4291. Many Thanks Eddie / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Cluster like installs
Thank you for your reply. I have now submitted the feature request for the SQL Backup Development Team to consider support for HP Polyserve and Neverfail clustering solutions. The reference for th...
0 votes
Hi Andrew Unfortunately SQL Backup does not officially support HP Polyserve and Neverfail clustering solutions and has not been tested on these two clustering solutions. The only course of action is to fail over the cluster and install SQL Backup onto the passive node, which will include another install of the extended stored procedures over the top of the existing items installed earlier. The SQL Backup Server components installer is cluster aware for Microsoft Windows Server 2003 and 2008 clusters, creating the SQL Backup Agent service on all nodes within the cluster, the SQL Backup resource within the Windows Cluster Administrator and the extended stored procedures into master database for the SQL instance. I can submit a feature request on your behalf for the development team to consider SQL Backup to support the HP Polyserve and Neverfail clustering solutions. However I cannot guarantee the success of the request and if approval is given, in what future version of SQL Backup the requested feature will appear in. Many Thanks Eddie / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Cluster like installs
Hi Andrew Unfortunately SQL Backup does not officially support HP Polyserve and Neverfail clustering solutions and has not been tested on these two clustering solutions. The only course of action ...
0 votes
Thank you for your suggestion. I have submitted a Feature Request for the SQL Response Development team to consider. The reference for this feature request is SSR-1625. I cannot guarantee that the feature request will be successful. If approval is given, what future version of SQL Response the requested feature will appear in. Many Thanks Eddie / comments
  1. Community
  2. SQL Monitor Previous Versions
  3. Enhancement - clear alerts using keyboard
Thank you for your suggestion. I have submitted a Feature Request for the SQL Response Development team to consider. The reference for this feature request is SSR-1625. I cannot guarantee that the...
0 votes
Thank you for your post into the forum. Unlike a SQL Cluster, unfortunately SQL Backup does not support SQL Server Database Mirroring. On a SQL Cluster both or all nodes of the cluster have an installation of SQL Backup Server components. The server components is cluster aware so all nodes of the cluster are installed simultaneously and a resource is created within the Cluster Administrator. A cluster applies to the whole SQL Instance not individual databases. A database mirror is configured per database. Both the Principal Server and the Mirror Server have there own independent installations of SQL Backup Server Components. The server components are not aware of the database mirroring. The Witness server will initiate fail over if a problem is detected, so that the mirror database becomes the principal. SQL Backup does not know if fail over has occurred, has no resource is created on the witness server. The same caveats apply to both native SQL Server Backup and Red Gate SQL Backup: 1. While database mirroring is active, you cannot backup or restore the mirror database. The Mirror database is in a NORECOVERY state, so SQL Server prevents backup's of this database. 2. Although you can backup the principal database, you cannot us BACKUP LOG WITH NORECOVERY 3. You cannot restore the principal database. The mirror will correct itself after failover. The only possible workaround for the problem is to create a backup job that perform a backup all databases on each server. Databases in a restoring state will be ignored. Possible SQL Backup syntax maybe as follows: EXECUTE master..sqlbackup '-SQL "BACKUP DATABASES [*] TO DISK = [<path to backup file location>] WITH COMPRESSION = 2, ERASEFILES = 2, COPYTO = [<unc path a network share>], VERIFY" ' Alternatively, you can use the EXCLUDE argument, which will backup all databases except those listed in the EXCLUDE argument. For example, you may just want to backup all user databases: EXECUTE master..sqlbackup '-SQL "BACKUP DATABASES EXCLUDE [master, model, msdb] TO DISK = [<path to backup file location>] WITH COMPRESSION = 2, ERASEFILES = 2, COPYTO = [<unc path a network share>], VERIFY" ' Once fail over occurs, the mirror database becomes the principal and therefore no longer in a restoring state and the database will then be backed up using SQL Backup. Many Thanks Eddie / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Sql Backup with Mirrored Server
Thank you for your post into the forum. Unlike a SQL Cluster, unfortunately SQL Backup does not support SQL Server Database Mirroring. On a SQL Cluster both or all nodes of the cluster have an inst...
0 votes
Hi Sorry that the deactivation has not worked for you. I have sent a Private Message (PM) requesting your contact details so I can create a support for you. Many Thanks Eddie / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Deactivate did not to work on SQL 2008 with Server 2008 OS
Hi Sorry that the deactivation has not worked for you. I have sent a Private Message (PM) requesting your contact details so I can create a support for you. Many Thanks Eddie
0 votes
Total activity
3017
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
1312