Comments
Sort by recent activity
Hello Peter,
I hope this clears things up for you: https://documentation.red-gate.com/sca3/developing-databases-using-sql-change-automation/validating-change-scripts/target-and-shadow-databases
The
important part here is that the "Target" is the development database,
not what you are deploying to - so if your target is always on your
local dev box, and you never point the Debug Target Connection String
at another server, then it will only ever create the xx_shadow on the
dev machine. Please let me know if this is helpful or if you have any more questions. Kind regards, Pete Ruiz / comments
Hello Peter,
I hope this clears things up for you: https://documentation.red-gate.com/sca3/developing-databases-using-sql-change-automation/validating-change-scripts/target-and-shadow-databases
Th...
Hi Chip, What version of SQL Backup are you
using? If not already, can you please confirm if the performance issues
exist on the latest version of SQL Backup? Can you please provide additional details about your source and target environments? Also, here a few suggestions on how you can optimize the backup speeds: https://documentation.red-gate.com/sbu10/troubleshooting/optimizing-backup-speed Lastly, can you please send over the log files? https://documentation.red-gate.com/sbu10/troubleshooting/sql-backup-log-files / comments
Hi Chip, What version of SQL Backup are you
using? If not already, can you please confirm if the performance issues
exist on the latest version of SQL Backup? Can you please provide additional de...
Hello Mike, In Tools>Extensions and Updates... there
should be the option to enable/ disable SQL Prompt when you right-click
the tool in the list. If you're using the Enterprise version of Visual
Studio, then I would also suggest uninstalling SQL Prompt Core first to
avoid any conflicts. Please see the image below: [image] Please let me know if this helps. Kind regards, Pete Ruiz / comments
Hello Mike, In Tools>Extensions and Updates... there
should be the option to enable/ disable SQL Prompt when you right-click
the tool in the list. If you're using the Enterprise version of Visual...
Hello Michael, This can happen if/when the
build process is interrupted. You would need to drop them manually in
these cases. Alternatively you can use the Temporary Database setting
which will always use the same database. You will need to pre-create this beforehand. Kind regards, Pete Ruiz / comments
Hello Michael, This can happen if/when the
build process is interrupted. You would need to drop them manually in
these cases. Alternatively you can use the Temporary Database setting
which will ...
Hello Delijah, Thanks for reaching out and sorry that you're having trouble with SQL Source Control. At this time we do not currently offer support for the TFS version of GIT (please see documentation).
I'm afraid that we don't have any plans to support this. There is a
significant known issue that authentication between TFS Git and SQL
Source Control does not work, so we can't support this at all. As the documentation suggests, "You can use the Git command line or another Git client to perform push/pull operations." Another
workaround is to link to a working folder, then use a third party tool
to push and pull to you're remote repository. I know this might be
tedious, very sorry for any inconvenience this might have caused. Please let me know if there are any more questions. Kind regards, Pete Ruiz / comments
Hello Delijah, Thanks for reaching out and sorry that you're having trouble with SQL Source Control. At this time we do not currently offer support for the TFS version of GIT (please see documentat...
Hi Gabriel, When setting the project options, you have the option to ignore migration scripts for databases which could significantly improve the performance. Please see the product documentation page for setting project options here. As
far as deleting them goes, assuming you don't need the migration
scripts, I have had instances where our customers would just delete all
of them. This step, however, should be taken with precaution. Kind regards, Pete Ruiz / comments
Hi Gabriel, When setting the project options, you have the option to ignore migration scripts for databases which could significantly improve the performance. Please see the product documentation p...
It seems that this is a known issue that is currently being
reviewed. You can reference this by SP-6989. I've went ahead and linked a
support ticket to this bug and will update you on it as it progresses.
Sorry for any inconvenience this might have caused. Please let me know
if there are any questions. Kind regards, Pete Ruiz Redgate Support
/ comments
It seems that this is a known issue that is currently being
reviewed. You can reference this by SP-6989. I've went ahead and linked a
support ticket to this bug and will update you on it as it pr...
Hello @jonathan.lee, This is an update for SP-7127. The team have just released a fix for this issue in SQL Prompt 9.4.7. Please update to this version and confirm that the issue has been corrected for yourself as well! Kind regards, Pete Ruiz / comments
Hello @jonathan.lee, This is an update for SP-7127. The team have just released a fix for this issue in SQL Prompt 9.4.7. Please update to this version and confirm that the issue has been corrected...
Hello Hakim, Unfortunately, SSDT compatibility in SQL Compare and SQL Source Control is an unsupported beta feature. At
this time there is no feature available to ignore this construct or to
replace "[$(LinkedServerName)]" with "LinkedServerName" at deployment
time." I'm not sure if this is helpful but you could possibly
ignore these all together by configuring a customer filter (might or
might not work): https://documentation.red-gate.com/sc13/reviewing-the-comparison-results/using-filters / comments
Hello Hakim, Unfortunately, SSDT compatibility in SQL Compare and SQL Source Control is an unsupported beta feature. At
this time there is no feature available to ignore this construct or to
repl...
Hello @dlrhosseinm
A support ticket was opened for the customer who reported this issue and was resolved.
The issue was caused by a stored procedure. The customer had to remove the offending object from source control and add re-add it.
Are you experiencing the same issue? If so, you can try the following: 1 - Unlink that database from Source Control 2 - Close SSMS 3 - Delete the contents of all subfolders inside %localappdata%\Red Gate\SQL Source Control 4\Caches (Please note that %localappdata% is a Windows Environment variable that usually corresponds to C:\Users\{username}\AppData\Local ) 4 - Use SQL Compare to synchronize your DB with the repository 5 - Relink DB with the repository
/ comments
Hello @dlrhosseinm
A support ticket was opened for the customer who reported this issue and was resolved.
The issue was caused by a stored procedure. The customer had to remove the offending obje...