an issue when deleting an image that has templates defined for it Fixed create image from backup if the size is more than 2TB Creating an
/clone2/release-notes-and-other-versions/sql-clone-2-release-notes
in the live application) and incrementing this new start-point by “1” for each key value to be replaced. At this point it is also worthwh
(or press Ctrl + Shift + P): image2016-3-16 14:24:8.png This unloads all database objects from memory. Connecting to a linked server Link
/sp7/managing-sql-prompt-behavior/managing-connections-and-memory
(or press Ctrl + Shift + P): image2016-3-16 14:24:8.png This unloads all database objects from memory. Connecting to a linked server Link
/sp8/managing-sql-prompt-behavior/managing-connections-and-memory
profiled. The profiler estimates this overhead and subtracts it from the timings, so in most cases results remain realistic. But for very
/app8/setting-up-and-running-a-profiling-session/choosing-application-types-and-settings
:<argfile> File containing the XML argument specification. /out:<fileName> Redirects console output to the specified file. /project:<proje
/app8/setting-up-and-running-a-profiling-session/profiling-from-the-command-line-api
of updating the database representation from the live database if the scan result is exactly the same as the previous one Fixes Changed m
/sql-data-catalog/release-notes/sql-data-catalog-1-release-notes
http://www.red-gate.com/products/SQL_Data_Compare/index.htm. These enable you to compare the contents (object schema, and data) of SQL Ba
. The Check for Updates message is now shown even in the case you haven’t installed any other Redgate products. Fixes to the Review differ
/rp/dlm-dashboard/release-notes/dlm-dashboard-1-2-release-notes
are short lived - ideally with a lifetime of less than 1 week - if only because they will keep on growing. Furthermore, it's very easy an
specific information on various components of the rule. All of the statistics fields are "live" and will constantly update as the rule is
/dms7/data-masker-help/major-data-masker-application-components/the-rule-statistics-tab
scripts, not a live database.
address of this machine cat <PUBLIC_KEY_FILEPATH> | ssh <USERNAME>@<REMOTE_HOST> "mkdir -p ~/.ssh && touch ~/.ssh/authorized_keys && chmo
will build and deploy the project to the live database specified in the database connection. # Path to a SQL Change Automation project $p
/sca3/developing-databases-using-sql-change-automation/deploying-sql-change-automation-projects
,keypassword:"p@ssword" prune:[true | false ], Enable / Disable pruning merge:[true | false ], Disable / Enable dependencies merging (Note
,keyfilename:file.pfx,keypassword:"p@ssword" prune:[true | false ], Enable / Disable pruning merge:[true | false ], Disable / Enable depen
not support comparing computed columns in scripts folders. When registering from a live database SQL Server itself can be queried to dete
/sdc14/working-with-other-data-sources/working-with-scripts-folders
can: test exactly what'll happen when you deploy to production without the risks associated with updating a live database test server con
/dlma1/tutorials/using-the-powershell-cmdlets/deploy-to-multiple-environments-using-octopus-deploy
live hardware and software. The preproduction (or "staging") environment is used for testing and should closely match the production envi
/dlma1/get-started/using-the-add-ons/use-the-vsts-release-extension
This worked example demonstrates a basic comparison and deployment of two SQL Server databases. In the example, the Magic Widget Company
/sc12/worked-examples/worked-example-comparing-and-deploying-two-databases
were made to the live database after Version 1.2 was released. This effectively created a new version of the schema outside of source con
/sca3/automating-database-changes/automated-deployments/handling-schema-drift
, the Magic Widget Company has a SQL Server database running on a live web server. This database contains a number of tables, views, store
information on various components of the rule. All of the statistics fields are "live" and will constantly update as the rule is executin
/dms6/data-masker-help/major-data-masker-application-components/the-rule-statistics-tab
estimates this overhead and subtracts it from the timings, so in most cases results remain realistic. But for very short-lived methods, f
/app9/setting-up-and-running-a-profiling-session/choosing-application-types-and-settings
:<argfile> File containing the XML argument specification. /out:<fileName> Redirects console output to the specified file. /project:<proje
/app9/setting-up-and-running-a-profiling-session/profiling-from-the-command-line-api
