User profile for Eddie D

Thank you for your post into the forum and sorry that you are experiencing this problem. How many concurrent SQL Backup tasks to you have running? Can you please check the SQL Server Error Logs, do you have any entries that are reporting locks or deadlocks to the msdb database by the SQBCoreService.exe? Many Thanks Eddie / comments

Thank you for your post into the forum and sorry that you are experiencing this problem. How many concurrent SQL Backup tasks to you have running? Can you please check the SQL Server Error Logs, do...

0 votes

Thank you for your post into the forum. The answer to question depends upon the importance placed upon the data in your database. This drives the decision on the types of backup you wish to perform. For a database whose data changes rarely or a small number of transaction occur per day, having the database in Simple Recovery model and performing a weekly Full Backup and a Differential Backup daily maybe sufficient. For a busy database that has many transaction a day, like an 'Orders' database and recovery to a point in time is required, having the database in the Full Recovery model will be required. One possible simple backup strategy would to perform a Full Backup twice a week, Differential Backup twice a day and Transaction Log backups every 15 minutes. By performing a transaction log backup, the DBA will be able to perform a point in time recovery. Another important point to consider is how quickly you wish to recover lost data and / or how much data are you willing to lose. SQL Server records every transaction in a write-ahead transaction log. The transaction log is a storage area that automatically tracks the changes to the database. The transaction is recorded to the transaction log before it is committed to the database. When using the Simple Recovery model, SQL Server itself manages the transaction log, the DBA can only perform Full and Differential Backup tasks. To recover the data, the DBA needs to restore the last Full Backup followed by the last Differential Backup. Therefore the database can only be recovered to the time of last Differential backup, so any transaction performed after the Differential backup may be lost. Using the Full Recovery, the DBA needs to administer and manage the transaction log. When you backup the transaction log, the backup stores the changes since the last transaction log backup and then truncates the log, which clears out transaction that hve been committed. To recover the database you would need to restore the last Full Backup, the last Differential Backup followed by an unbroken chain of log backup taken since the last differential backup. By performing regular log backups, you improve the performance of your database. If a transaction log backup has never been performed, it is possible for your transaction log file to keep growing until you run out of disk space. You are incorrect in your analysis regarding a Differential Backup: A differential captures data that has changed since last differential correct? A Differential is all the changes committed to a database since the last Full Backup. Therefore the size of each Differential Backup file continues to grow until the next Full Backup is taken. Log Shipping is one possible solution for providing High Availability solution, by log shipping the transaction log to a standby server, you have an up to date copy of your database. In the event of failure of the primary production database. You can bring the secondary database on line to take over from the failed primary. Many Thanks Eddie / comments

Thank you for your post into the forum. The answer to question depends upon the importance placed upon the data in your database. This drives the decision on the types of backup you wish to perfor...

0 votes

Thank you for your reply. I have submitted a feature request for the development team to consider, for SQL Prompt so users can add SQL instances that wish to ignore. The reference number for this request is SP-2802. Hopefully the requested feature will appear (or return, depending on your point of view) in a future version of SQL Prompt. Many Thanks Eddie / comments

Thank you for your reply. I have submitted a feature request for the development team to consider, for SQL Prompt so users can add SQL instances that wish to ignore. The reference number for this ...

0 votes

Thank you for your reply. The option to exclude SQL Prompt accessing SQL instances has been removed. Is this an option you would like to see returned to the product? Many Thanks Eddie / comments

Thank you for your reply. The option to exclude SQL Prompt accessing SQL instances has been removed. Is this an option you would like to see returned to the product? Many Thanks Eddie

0 votes

Thank you for your post into the forum. There is no longer cache management in SQL Prompt V4. The SQL Prompt caching mechanism was modified or improved with the release of SQL Prompt V4, so the cache management settings in Version 3 no longer apply. If you are writing a query on a database while someone else is making changes to the structure of that database, the suggestions offered by SQL Prompt may become out of date. For example, if someone has added several tables to the database while you have been connected to that database, these tables will not appear in the suggestions box. To reload the database objects, on the SQL Prompt 4 menu, select Refresh Suggestions or press Ctrl + Shift + D. Any changes to the database structure will now be reflected in the suggestions box. You should also refresh suggestions when you have created a new object in the current query, and executed that block of code. For example, if you create a table NewObject and execute the statement, then continue to write the query, the NewObject table will not appear in the suggestions box until you refresh the suggestions. Refreshing suggestions applies only to the database to which you are currently connected. SQL Prompt automatically refreshes a database's objects when you close down your query editor application, then re-open it and re-connect to that database. I hope the above answers your question. Many Thanks Eddie / comments

Thank you for your post into the forum. There is no longer cache management in SQL Prompt V4. The SQL Prompt caching mechanism was modified or improved with the release of SQL Prompt V4, so the cac...

0 votes

Thank you for your post into the forum. I suspect that you are using either Microsoft® Visual SourceSafe® versions 6.0d and 2005 or Microsoft® Visual Studio® 2005 Team Foundation Server SP1. I believe that it is a requirement of the above source control systems, that the files are checked out before being modified. Unfortunately there is not an option that can be set to automatically checkout the files from the source control application. However I can submit a feature request for the development team to consider to add this feature, if you so wish? Many Thanks Eddie / comments

Thank you for your post into the forum. I suspect that you are using either Microsoft® Visual SourceSafe® versions 6.0d and 2005 or Microsoft® Visual Studio® 2005 Team Foundation Server SP1. I beli...

0 votes

Thank you for your post into the forum. SQL Backup has two major components: SQL Backup GUI - Used for managing and creating the SQL Backup jobs. This component is not licensed and can be installed on as many workstations and servers as required. SQL Backup Server Components - This component includes the SQL Backup Agent Service and the Extended Stored Procedures that perform the actual backup and restore processes. This is the licensed component of SQL Backup. SQL Backup Server Components are licensed, for want of a better term, per Windows Instance. So if you have two Windows instances running on one physical machine and you require SQL Backup Server Components to be on both Windows instances, you will need a two licenses of SQL Backup one for each Windows Instance. If you have multiple SQL instances on 1 Windows Instance, you will only require a single license for that Windows instance SQL Backup for a 5 server license is supplied with 5 allowed distinct activations. So you will be able to activate 5 distinct Windows instances. The activation process will fail for the 6th server and the error message returned will inform you that you have attempted to activate the license serial number on too many machines. If you need move a license from one Windows Instance to another, for example you are decommissioning that machine. You can deactivate the license and then transfer it to the replacement machine. I hope the above answers your question. Many Thanks Eddie / comments

Thank you for your post into the forum. SQL Backup has two major components: SQL Backup GUI - Used for managing and creating the SQL Backup jobs. This component is not licensed and can be installe...

0 votes

Thank you for your post. Unfortunately this feature is not in SQL backup V5.4 or earlier. The featture to automatically kill database connections prior to a restore is a new feature to SQL Backup Version 6. If you have need of this feature please either upgrade to SQL backup V6, or use the information in this knowledge base ARTICLE. Many Thanks Eddie / comments

Thank you for your post. Unfortunately this feature is not in SQL backup V5.4 or earlier. The featture to automatically kill database connections prior to a restore is a new feature to SQL Backup V...

0 votes

Hi Are you still having problems with this Alert that keeps repeating? Or did recycling the error log resolve the problem? Many Thanks Eddie / comments

Hi Are you still having problems with this Alert that keeps repeating? Or did recycling the error log resolve the problem? Many Thanks Eddie

0 votes

Thank you your post into the forum. You do not need to remove registered servers. The upgrade from SQL Backup V5.4 to Version 6.3 is a two part process. You will need to upgrade both the SQL Backup GUI and the server components. So on the server that has a GUI and the only registered server is the local server, no problem simply upgrade the GUI and deploy the server componets to the registered server. On the machine that has multiple servers registered. Upgrade the SQL Backup GUI and then deploy the Server components to each of the registered servers. When you first re-open the GUI after upgrading it , it will bring a reminder box that the server components need to be upgraded. When you view the regsitered server, a cog icon will be displayed to the right of the server to indicate that an upgrade is available. If you have already upgraded the server components for the registered server, there will be no cog icon to the right of the server name in the registered servers panel. A new feature added to SQL Backup V6.3 is the ability to activate multiple servers, so if you have multiple servers regsitered into the GUI registered servers panel form the Tools menu ->Utilities ->Multi-server Activation. This new feature maybe useful to you, as by applying SQL Backup V6.*, activation is set back to trail license and you will need to re-activate after upgrading. This sticky forum post contains a link to a pdf document that contains upgrade instructions. It was originally written for upgrading to SQL backup V6.0/6.1 from previous versions. However the advice is still valid for you upgrading from V5.4 to V6.3: http://www.red-gate.com/messageboard/vi ... php?t=9346 Many Thanks Eddie / comments

Thank you your post into the forum. You do not need to remove registered servers. The upgrade from SQL Backup V5.4 to Version 6.3 is a two part process. You will need to upgrade both the SQL Backu...

0 votes

How can we help you today?

Eddie D

Comments