Activity overview
Latest activity by stanori
Hello,
Thanks for your forum post. Within SQL Monitor we have the ability to show you the top 10 queries. See this article below for more details: https://documentation.red-gate.com/disp ... iagnostics
We currently do not have the ability to display more than 10 in our most recent version. However, if you would like to pull this from SQL Server, here is an article that contains a sample query that you could modify to help you pull the top 100 queries:(example gives Top 10) http://serverfault.com/questions/162245 ... sql-server
Hope this helps.
Best Regards,
Steve / comments
Hello,
Thanks for your forum post. Within SQL Monitor we have the ability to show you the top 10 queries. See this article below for more details:https://documentation.red-gate.com/disp ... iagnost...
Hello,
Sorry to hear about that. I went back and confirmed, actually the ctrl-enter was for older versions of SQL Doc(v2). I tried this out in SQL Doc 3 and confirmed this no longer works. Ive logged a bug under SDOC-1628 in regards to this issue with the line break.
In terms of the actual timelines for next planned release, we do not have any short term plans for a new release, however, I would suggest periodically checking in on the status, or checking out our roadmap here for current development and planned releases: http://www.red-gate.com/our-company/about/news/
Sorry about the inconvenience.
Best Regards,
Steve / comments
Hello,
Sorry to hear about that. I went back and confirmed, actually the ctrl-enter was for older versions of SQL Doc(v2). I tried this out in SQL Doc 3 and confirmed this no longer works. Ive logg...
Hello,
Thanks for your post. Sorry about the troubles you are having with SQL Doc. I have logged a bug report for your last 3 issues, and the first one, please see below:
1. For this issue you can workaround it by typing "ctrl-enter" for line breaks in the description
2. This has been logged as a bug under SDOC-1625
3. This has been logged as a bug under SDOC-1626
4. This has been logged as a bug under SDOC-1627
In regards to the bugs, these will be reviewed by our Product Managers to determine if and when these might be implemented in future versions of the tool. Sorry about the inconvenience this may be causing.
Best Regards,
Steve / comments
Hello,
Thanks for your post. Sorry about the troubles you are having with SQL Doc. I have logged a bug report for your last 3 issues, and the first one, please see below:
1. For this issue you can ...
Hello,
Thanks for the update. You are correct in that the update will work and the query does look a bit incorrect with the customer ID listed twice. We have this logged as a bug under SDC-1087 to look at for future versions. It should not prevent the deployment script from executing. Sorry about the inconvenience.
Best Regards,
Steve / comments
Hello,
Thanks for the update. You are correct in that the update will work and the query does look a bit incorrect with the customer ID listed twice. We have this logged as a bug under SDC-1087 to ...
Hello,
Thanks for contacting us via the forums. I did some research on this issue and it looks like we have seen this when specifying the keyword "where" in the where clause editor.
To fix this issue:
- Open the where clause editor
- Change "WHERE Customer_ID = 11" to "Customer_ID = 11"
That should fix the deployment script from entering the "where" twice.
Hope this helps!
Best Regards,
Steve / comments
Hello,
Thanks for contacting us via the forums. I did some research on this issue and it looks like we have seen this when specifying the keyword "where" in the where clause editor.
To fix this iss...
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 ...