Comments
Sort by recent activity
Hi Dragan,
Thanks for your post. In regards to this specific error "Tcp provider error 0 - the semaphore timeout period has expired " this is a commonly caused by an intermittent network issue or SQL Server that is experiencing issues with hardware or being overloaded.
Here is an additional link that can help with troubleshooting these types of generic connection errors: http://sqlserverscribbles.com/2013/02/1 ... s-expired/ http://social.technet.microsoft.com/For ... as-expired
Another suggestion you could try is running SQL Data Compare directly on the machine of one of your DB sources to see if the same issue occurs.
Hope this info helps.
Best Regards,
Steve / comments
Hi Dragan,
Thanks for your post. In regards to this specific error "Tcp provider error 0 - the semaphore timeout period has expired " this is a commonly caused by an intermittent network issue or S...
Hello,
Thanks for your post. In regards to your question about backing up Azure databases, we have an SQL Azure offering here: http://cloudservices.red-gate.com/
(If you are looking to backup databases that are located in a virtualized environment that is hosted in the Azure cloud, then as long as you can connect to it via SSMS and have the ability to install Windows Services (for our SQL Backup Agent) you can use SQL Backup Pro)
Best Regards,
Steve / comments
Hello,
Thanks for your post. In regards to your question about backing up Azure databases, we have an SQL Azure offering here:http://cloudservices.red-gate.com/
(If you are looking to backup databa...
Hi Bellisio,
Thanks for your post. In regards to your particular question about migrating the history and source control contents of your TFS repository, we do not have any specific recommendations on the actual migration of the repo contents as this is something specific to the TFS backend. Here are some links to help get you started on the migration within TFS: http://msdn.microsoft.com/en-us/library/ms404883 http://stackoverflow.com/questions/6776 ... to-another
When working in SQL Source Control, the following steps are recommended for your situation:
- unlink the affects DB's prior to the repo move
- Make the change in repo location
- Once the repo is located at it's new location: relink the affected DB's in SSMS
(The relinking will rebuild the underlying working base and transient folders on the local machine where SQL Source Control is installed)
The important part to note is that the history of the changes is read from TFS directly, so if the history is lost within the actual source control backend, SQL Source Control will not be able to read in the history. Hope this helps a little.
Best Regards,
Steve / comments
Hi Bellisio,
Thanks for your post. In regards to your particular question about migrating the history and source control contents of your TFS repository, we do not have any specific recommendations...
Hi aspillert,
Thanks for the post. In your particular situation, there are a few options available that you can try to tackle this scenario.
First possibility:
- Create a filter that contains a rule that includes just views that start with v. Here is an article about setting up filters: https://documentation.red-gate.com/disp ... ng+filters
- once the filter is setup you can then save the settings as a project and then the next time you want to run the comparison you can setup a cmd line job to run sql compare and make use of the project file
Second possibility:
- create a command line job that makes use of the /include(or vice versa the /exclude switch) to include just certain object types or object names in the command. Here are some more details about setting up the command line: https://documentation.red-gate.com/disp ... mmand+line
Along with these different solutions, it is also important to note that which ever method you go with, part of the designed behavior of SQL Compare is that it will need to register each database source each time a comparison is run. The number of objects in a database source can increase the amount of time it takes to process a comparison. This database registration is a required step of the application so that it can understand the current state of your database schema and dependencies.
I hope this helps.
Best Regards,
Steve / comments
Hi aspillert,
Thanks for the post. In your particular situation, there are a few options available that you can try to tackle this scenario.
First possibility:
- Create a filter that contains a rul...
Hi manoloaloe,
Sorry to hear about the error you are having with the TFS server. These particular errors are coming back as a result of the policy configuration on the TFS server. With version 3.3 and later of SQL Source Control, the particular policies are enforced.
To workaround this issue, you can disable the policy checks by following this article: http://documentation.red-gate.com/displ ... y+checking
Best Regards,
Steve / comments
Hi manoloaloe,
Sorry to hear about the error you are having with the TFS server. These particular errors are coming back as a result of the policy configuration on the TFS server. With version 3.3 ...
Hi Ed,
Thanks for your post. The log files for the SQL Monitor installation can be found in the following location (win7/8/2008/2012) machine:
c:\program data\Red Gate\logs\SQL Monitor 4
Note: The program data is hidden by default in most of the Windows default installation and you will need to enable show hidden files.
Hope this helps.
Best Regards,
Steve / comments
Hi Ed,
Thanks for your post. The log files for the SQL Monitor installation can be found in the following location (win7/8/2008/2012) machine:
c:\program data\Red Gate\logs\SQL Monitor 4
Note: The ...
Hello,
I have an update with regards to this issue. It looks like we have some conflicting releases of SIP framework that may have contributed to this issue.
Here is another fix if the previous one does not work:
- delete: C:\ProgramData\Red Gate\SIPFw
-install/update dependency tracker from here: http://download.red-gate.com/EAP/SQLDep ... .1.164.exe
The update in the link above has the new SIP framework included which should resolve this.
Best Regards,
Steve / comments
Hello,
I have an update with regards to this issue. It looks like we have some conflicting releases of SIP framework that may have contributed to this issue.
Here is another fix if the previous one...
Hi,
Thanks for your post regarding SQL Test. It could be that there is a conflict with the SSMS toolbar.
You could try the following to resolve:
- Uninstall SQL Test and SSMS Integration Pack and SSMS Integration Framework(if present) To uninstall->Control Panel->Programs and Features
- Reinstall SQL Test from the latest version of the developer bundle installer: http://www.red-gate.com/dynamic/product ... /download#
Hope this helps.
Best Regards,
Steve / comments
Hi,
Thanks for your post regarding SQL Test. It could be that there is a conflict with the SSMS toolbar.
You could try the following to resolve:
- Uninstall SQL Test and SSMS Integration Pack and S...
Hi rachana21885,
Thanks for your post. It sounds like your IIS is having some configuration issues. We have opened a support request and will be in contact with you soon.
Best Regards,
Steve / comments
Hi rachana21885,
Thanks for your post. It sounds like your IIS is having some configuration issues. We have opened a support request and will be in contact with you soon.
Best Regards,
Steve
Hi fingers,
The advantage of the Red Gate built in web server is that it comes pre-configured to work with SQL Monitor much easier out of the box. The IIS option is available, however, it requires some deeper technical knowledge and expertise on IIS to get up and running. In terms of performance there is no advantage of one over the other in most scenarios.
Best Regards,
Steve / comments
Hi fingers,
The advantage of the Red Gate built in web server is that it comes pre-configured to work with SQL Monitor much easier out of the box. The IIS option is available, however, it requires ...