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

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

  1. SQL Doc 3.0 release notes

    printer settings SDOC-1273 "Invalid characters in path" error when creating HTML SDOC-1292 No option to go back to connection pane if con

    /sdoc5/release-notes-and-other-versions/sql-doc-3-0-release-notes

  2. Masking Primary Key

    . Then go to the Change Manager tab and click on Convert to Sync Manager image2022-11-8_10-26-39.png Step 3: Now you have the basis of a S

    /dms7/data-masker-help/general-topics/validation/masking-primary-key

  3. Managing your Redgate ID

    , or you first logged a Redgate support request. Creating a Redgate ID If you don’t already have a Redgate ID, you can create one: Go to t

    /xx/licensing/managing-your-redgate-id

  4. Set up the VSTS Build extension

    This page shows how to install the DLM Automation VSTS Build extension If you are using non-hosted VSTS Agents, you need to install DLM A

    /dlma1/install/set-up-the-vsts-build-extension

  5. Set up the TFS Build plugin

    the latest version of DLM Automation. Go to the DLM Automation add-ons webpage http://www.red-gate.com/dlmas/add-ons-page. In the Microso

    /dlma1/install/set-up-the-tfs-build-plugin

  6. Set up the TFS MSBuild scripts

    https://documentation.red-gate.com/display/DAS/Installing. Go to the DLM Automation add-ons webpage http://www.red-gate.com/dlmas/add-ons

    /dlma1/install/set-up-the-tfs-msbuild-scripts

  7. Set up the VSTS Release extension

    This page shows how to install the DLM Automation VSTS Release extension If you are using non-hosted VSTS Agents, you need to install DLM

    /dlma1/install/set-up-the-vsts-release-extension

  8. Use the TFS MSBuild scripts

    DLMAutomation.test.properties DLMAutomation.sync.properties DLMAutomation.publish.properties In this example, we're going to configure th

    /dlma1/get-started/using-the-add-ons/use-the-tfs-msbuild-scripts

  9. Viewing component information and log files

    Log files collect information about SQL Monitor while you are using it. These files are useful if you have a problem. To download the log

    /sm8/advanced-operations/viewing-component-information-and-log-files

  10. Changing the transaction isolation level

    When doing a Get Latest, by default SQL Source Control uses the READ COMMITTED transaction isolation level. You can change this by editin

    /soc4/options/changing-the-transaction-isolation-level

  11. Disabling TFS policy checking

    If you don't want your commits to have to conform to TFS policies, you can stop SQL Source Control checking for TFS policies by editing a

    /soc4/options/disabling-tfs-policy-checking

  12. Changing the number of revisions shown in the History dialog box

    By default, the History dialog box shows all the revisions made to the selected database. You can change the number of revisions shown by

    /soc4/options/changing-the-number-of-revisions-shown-in-the-history-dialog-box

  13. Viewing component information and log files

    Log files collect information about SQL Monitor while you are using it. These files are useful if you have a problem. To view the log fil

    /sm11/maintaining-and-upgrading-sql-monitor/maintaining-sql-monitor/viewing-component-information-and-log-files

  14. Working with migration scripts

    Control window opens. Go to the Migrations tab. Select the type of migration script, depending on your development process and the change

    /soc6/common-tasks/working-with-migration-scripts

  15. Link to a working folder

    to link this database, add the database objects to source control. To do this, go to the Commit tab and save the objects to the script fo

    /soc6/linking-to-source-control/other-source-control-systems/link-to-a-working-folder

  16. Link to TFS

    to source control in an 'initial commit'. To do this, go to the Commit tab and commit the objects. For more details, see Your first commi

    /soc6/linking-to-source-control/link-to-tfs

  17. How SQL Source Control works behind the scenes

    database and goes to the Commit changes tab. If we compare Amanda's database and the scripts folder in source control, we can see a table

    /soc4/troubleshooting/how-sql-source-control-works-behind-the-scenes

  18. Branching and merging

    control project on the right-click menu. Create a new source control project linking the schema to the trunk. Go to the Check in tab. The

    /soco6/working-with-source-control-systems/branching-and-merging

  19. Deploying to a single environment using Octopus Deploy

    and other resources). You can look at an HTML report to see what'll be added, removed or modified if you go ahead with deployment, and ch

    /sr1/worked-examples/deploying-to-a-single-environment-using-octopus-deploy

  20. Use-DlmDatabaseRelease

    , if the database goes offline). After executing the script, the cmdlet checks that the target database schema has updated correctly to th

    /sr1/cmdlet-reference/use-dlmdatabaserelease

  21. Walkthrough: Using SQLCover with DLM Automation PowerShell cmdlets

    \nuget.exe" # Specify the location of nuget.exe # Pull down ReportGenerator to the PackagesDir using NuGet & $nuget install ReportGenerato

    /dlma1/tutorials/walkthrough-using-sqlcover-with-dlm-automation-powershell-cmdlets

  22. Generating debugging information

    Generating a .pdb file allows you to debug the resulting assembly in an IDE. To generate debugging information, in the Project Settings w

    /sa8/building-your-assembly/generating-debugging-information

  23. Obfuscating your application's control flow

    Control obfuscation changes the code inside your methods, converting it into 'spaghetti code'. To use control flow obfuscation, in the Pr

    /sa8/obfuscating-your-code-with-smartassembly/obfuscating-your-application-s-control-flow

  24. Creating a proxy for external calls

    SmartAssembly. Using the references dynamic proxy To use hide external calls, in the Project Settings window, go to References Dynamic Pr

    /sa8/obfuscating-your-code-with-smartassembly/creating-a-proxy-for-external-calls

  25. Assigning a strong name key

    Signing your assembly with a strong name key protects the assembly's name, and prevents modification of the assembly. To use strong name

    /sa8/obfuscating-your-code-with-smartassembly/assigning-a-strong-name-key


Didn't find what you were looking for?