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

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

  1. Installation

    of the database being cloned is going to be used from the same SQL Server instance as the source database then only one Agent needs to be

    /clone5/getting-started/installation

  2. Tutorial - Repeatable Migrations

    will be similar to the regular migrations, except for the V prefix which is now replaced with a R and the lack of a version. So go ahead

    /fd/tutorial-repeatable-migrations-184127625.html

  3. Tutorial - Undo Migrations

    for the V prefix which is now replaced with a U. So go ahead and create U2__Add_people.sql in the /sql directory: DELETE FROM PERSON; And

    /fd/tutorial-undo-migrations-184127627.html

  4. Setting up Slack notifications

    . Configuring Slack notifications Go to the Configuration tab. Under Alerts and Metrics, select Notification settings: ConfigurationScreen

    /sm10/metrics-alerts-and-notifications/configuring-alert-notifications/setting-up-slack-notifications

  5. Deploy a database package to a single environment using Octopus Deploy

    the "Download and extract database package" step This step picks up the NuGet package of the database schema you're going to deploy. In t

    /dlma1/tutorials/using-the-powershell-cmdlets/deploy-a-database-package-to-a-single-environment-using-octopus-deploy

  6. Walkthrough: Using SQLCover with DLM Automation PowerShell cmdlets

    & $nuget install ReportGenerator -Version 2.4.4 -o $PackagesDir # The ReportGenerator executable $reportGeneratorExe = "$PackagesDir\Repo

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

  7. Understanding memory problems

    over time. Memory use increases whenever you carry out a specific action. Memory use doesn't go back to the same level after the action i

    /amp8/understanding-memory-problems

  8. 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

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

  9. 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

    /soc7/configuring/move-the-working-base

  10. Teams using the dedicated model

    free to develop complex changes that might cause other parts of the database or the application to break. If something goes wrong, it doe

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

  11. Git

    the steps described below. Adding Git to your path In Control Panel go to System and select Advanced system settings. Click Environment V

    /soc7/requirements-and-supported-systems/git

  12. Logging and log files

    problem, you may want to change the amount of logging. Changing the log level Close SQL Server Management Studio. Go to the SQL Source Co

    /soc7/troubleshooting/logging-and-log-files

  13. 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

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

  14. 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

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

  15. 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

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

  16. 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

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

  17. The call graph

    are calculated. The timing mode dropdown menu controls the way in which method timings are calculated. If you want to include blocking su

    /app10/working-with-profiling-results/the-call-graph

  18. ANTS Performance Profiler 7.0 release notes

    or later: Attach to process The following features require Windows Vista or later: File I/O counters SQL counters Supported Visual Studio

    /app10/release-notes-and-other-versions/ants-performance-profiler-7-0-release-notes

  19. LCK_M_IS

    whether memory problems or I/O bottlenecks are causing locks to be held for longer than usual: Machine: memory used Memory pages/sec Disk

    /sm13/lck_m_is-195789626.html

  20. LCK_M_IU

    problems or I/O bottlenecks are causing locks to be held for longer than usual: Machine: memory used Memory pages/sec Disk avg. read time

    /sm13/lck_m_iu-195789627.html

  21. LCK_M_RIn_NL

    behavior: Lock timeouts/sec Lock timeouts/sec Avg. lock wait time On the Analysis page, check these metrics to see whether memory problem

    /sm13/lck_m_rin_nl-195789629.html

  22. LCK_M_RIn_S

    Lock timeouts/sec Avg. lock wait time On the Analysis page, check these metrics to see whether memory problems or I/O bottlenecks are cau

    /sm13/lck_m_rin_s-195789630.html

  23. LCK_M_RIn_U

    timeouts/sec Lock timeouts/sec Avg. lock wait time On the Analysis page, check these metrics to see whether memory problems or I/O bottle

    /sm13/lck_m_rin_u-195789631.html

  24. LCK_M_RIn_X

    timeouts/sec Avg. lock wait time On the Analysis page, check these metrics to see whether memory problems or I/O bottlenecks are causing

    /sm13/lck_m_rin_x-195789632.html

  25. LCK_M_RS_S

    : Lock timeouts/sec Lock timeouts/sec Avg. lock wait time On the Analysis page, check these metrics to see whether memory problems or I/O

    /sm13/lck_m_rs_s-195789633.html


Didn't find what you were looking for?