Search for " þ˸ ¹ Ʊ׶󱸸ó.p-e.kr ¶ ߱ġó ͳ Ʊ׶Ǹ ̵巹ǰ ͳ Ʊ׶Ǹ ͳ ó Ʊ׶ ʸ " returned 2309 results.

Search all the documentation for " þ˸ ¹ Ʊ׶󱸸ó.p-e.kr ¶ ߱ġó ͳ Ʊ׶Ǹ ̵巹ǰ ͳ Ʊ׶Ǹ ͳ ó Ʊ׶ ʸ "

  1. Teams using the dedicated model

    of the database or the application to break. If something goes wrong, it doesn't affect other developers. Visibility of what's been chang

    /soc6/sql-source-control-for-teams/teams-using-the-dedicated-model

  2. Teams using the shared model

    that the shared database was linked to. Go to the Get latest tab and get the changes. The new database is updated with the changes from t

    /soc6/sql-source-control-for-teams/teams-using-the-shared-model

  3. Link to an SSDT project

    in the Object Explorer, go to SQL Source Control. On the Setup tab, click Link to source control. On the Choose your source control syste

    /soc6/linking-to-source-control/link-to-an-ssdt-project

  4. Disable TFS policy checking

    TFS policy enforcement is only available in SQL Source Control version 3.3 and later. If you don't want your commits to have to conform t

    /soc6/configuring/disable-tfs-policy-checking

  5. Upgrading from old versions of migration scripts

    a suitable time before starting the upgrade process. To upgrade existing migration scripts: In the SQL Source Control window, go to the C

    /soc6/common-tasks/working-with-migration-scripts/upgrading-from-old-versions-of-migration-scripts

  6. Move the working base

    for the database (a new one will be created later). Close Management Studio. Go to the SQL Source Control config files folder. By default

    /soc6/configuring/move-the-working-base

  7. Checking unmanaged memory usage

    be the cause of a problem. Go back to where your code uses that module, and check that it's being called correctly. For example, there ma

    /amp/strategies-for-memory-profiling/checking-unmanaged-memory-usage

  8. Viewing the SQL differences

    :38:58.png Next and image2016-8-31 10:38:49.png Previous to go to lines that contain a difference. You can also use Alt + Up Arrow and Alt

    /sc13/reviewing-the-comparison-results/viewing-the-sql-differences

  9. Setting up a project with a SQL Source Control project in SSMS

    going to filter out a DDL trigger from our baseline of the existing database. We have specified a SQL Compare filter file, Filter.scpf …

    /sca4/developing-databases/working-with-the-ssms-add-in/setting-up-a-project-in-ssms/setting-up-a-project-with-a-sql-source-control-project-in-ssms

  10. Use the TFS Build plugin

    . Execute the following SQL query to create the WidgetCI database: CREATE DATABASE WidgetCI GO USE WidgetCI GO ALTER DATABASE WidgetCI SET

    /dlma2/get-started/using-the-add-ons/use-the-tfs-build-plugin

  11. Version control

    changes to check that the project still builds successfully. You can do this by going back to the Generate Migrations tab, which will cle

    /fd/version-control-138347113.html

  12. Moving the Base Monitor to a different machine

    to decommission, To do this, go to Services (select Start > Run, enter services.msc and click OK) and stop SQL Monitor Base Monitor. Opti

    /sm13/moving-the-base-monitor-to-a-different-machine-195790020.html

  13. The Run Statistics Tab

    graphic was a bit of artwork placed on the Run the Masking Set button on an early version of the Data Masker software. We were going to l

    /dmo5/data-masker-for-oracle-help/major-data-masker-application-components/the-run-statistics-tab

  14. Rule Blocks and Dependencies

    everything and go back and reconcile the where clauses method avoids the classic Where Clause Skip Error it which it is assumed that the

    /dmo5/data-masker-for-oracle-help/general-topics/rule-blocks-and-dependencies

  15. Suggested Rules for the Scott Sample schema

    : Rule 20-0005 masks the COMM field in all rows in the table using the Null Values dataset to remove the contents. Then rule xx-0006 goes

    /dmo5/data-masker-for-oracle-help/sample-masking-sets-and-schemas/suggested-rules-for-the-scott-sample-schema

  16. Branching and merging

    repository. Get the latest version and commit any outstanding changes. Unlink the database from the branch. Relink the database to the tr

    /soc4/using-sql-source-control/branching-and-merging

  17. Object changed by Unknown

    the default trace. To add these permissions, your system administrator needs to go to each user's login (Security > Logins on the server

    /soc4/troubleshooting/object-changed-by-unknown

  18. Logging and log files

    |Performance Testing |33 |#33:Guid=b3e1aae0-9c1a-46f3-abda-e1e96a90fd1f:NumberOfSteps=0 Changing the log level Close Management Studio. G

    /soc4/troubleshooting/logging-and-log-files

  19. Logging changes to shared databases

    . Go to the SQL Source Control config files folder: %localappdata%\Red Gate\SQL Source Control 4 Open RedGate_SQLSourceControl_Engine_Engi

    /soc4/options/logging-changes-to-shared-databases

  20. What migration scripts do

    We're going to remove the migrations V2 beta from SQL Source Control in version 5. We're replacing it with an improved version of the ori

    /soc4/using-sql-source-control/working-with-migration-scripts/migration-scripts-v2-beta/what-migration-scripts-do

  21. Rewinding time with Back in Time mode

    -23_16-47-43.png You can use the drop down to select the last 6, 12, or 24 hours, 2 days or 3 days. If you need to go further back in time

    /sm9/overview-pages/rewinding-time-with-back-in-time-mode

  22. Can't connect to Active Directory authentication service

    : USE [RedGateMonitor] GO DELETE FROM [settings].[KeyValuePairs] WHERE [KeyName] = 'ActiveDirectory-Enabled' OR [KeyName] = 'ActiveDirecto

    /sm9/troubleshooting/error-messages/can-t-connect-to-active-directory-authentication-service

  23. Adding a VMWare host

    collecting data. These tasks can be performed in either order, so, if you want to add VMware support to your existing hosts, you only nee

    /sm9/configuring-sql-monitor/adding-a-vmware-host

  24. Checking unmanaged memory usage

    be the cause of a problem. Go back to where your code uses that module, and check that it's being called correctly. For example, there ma

    /amp10/strategies-for-memory-profiling/checking-unmanaged-memory-usage

  25. Suggested Rules for the DMTest Sample Database

    : Rule 01-0004 masks the customer_firstname field in all rows in the table using the Male First Names dataset. Then rule xx-0005 goes back

    /dms7/data-masker-help/sample-masking-sets-and-databases/suggested-rules-for-the-dmtest-sample-database


Didn't find what you were looking for?