Search for " ξ渶õ rge117.top ¶ΰ渶 Ʈ λݿ渶 ̺ ְ ¶ΰ ǽð߱߰" returned 1050 results.

Search all the documentation for " ξ渶õ rge117.top ¶ΰ渶 Ʈ λݿ渶 ̺ ְ ¶ΰ ǽð߱߰"

  1. Restoring backups - destination database

    WITH REPLACE in a T-SQL RESTORE statement. Refer to your SQL Server documentation http://msdn2.microsoft.com/en-us/library/bb545450.aspx

    /sbu7/restoring/restoring-backups/restoring-backups-destination-database

  2. Excluding objects from script verification

    In some situations, it can be desirable to exclude certain objects or T-SQL batches from the project verification process. In particular,

    /sca4/developing-databases/concepts/verifying-projects/excluding-objects-from-script-verification

  3. Dedicated databases when switching branches

    -container $STANDBY_NAME -o json | jq .password -j)" PORT="$(rgclone.exe get data-container $STANDBY_NAME -o json | jq .port -j)" HOST="$(

    /fd/dedicated-databases-when-switching-branches-146211069.html

  4. Working with SSMS Tab Management (Quick Ref)

    History will restore all the tabs you had open when SSMS was last alive. The application saves all the T-SQL code, just as it was before

    /sp9/ssms-tab-management/working-with-ssms-tab-management-quick-ref

  5. Working with SSMS Tab Management (Quick Ref)

    loss of work. If SSMS crashes, or if you close down SSMS without saving your open tabs then, on relaunch, SQL Prompt Tab History will res

    /sp10/ssms-tab-management/working-with-ssms-tab-management-quick-ref

  6. Using a SQL Clone image as a baseline

    which do not defer name resolution https://www.sqlservercentral.com/articles/watching-out-for-deferred-name-resolution when created in T-

    /sca4/developing-databases/concepts/baseline/using-a-sql-clone-image-as-a-baseline

  7. Create a custom metric and alert

    the T-SQL query on which the metric is based. Step 2. Add an alert – optionally base an alert on the metric by completing sections simila

    /sm11/metrics-alerts-and-notifications/adding-custom-metrics-and-alerts/create-a-custom-metric-and-alert

  8. How SQL Monitor connects to monitored servers

    , plus T-SQL queries that access various SQL Server Dynamic Management Views and system catalog views, tables and properties. It may also

    /sm11/adding-and-managing-monitored-servers/how-sql-monitor-connects-to-monitored-servers

  9. Variables

    project to produce the package deployment T-SQL script and accompanying PowerShell script (i.e. VariableSampleProj_Package.sql

    /rr1/key-concepts/variables

  10. Getting better performance out of SQL Data Compare

    a T-SQL WHERE clause in the box: image2016-9-1 11:5:19.png You can apply the same WHERE clause to multiple tables, by highlighting the re

    /sdc13/getting-more-from-sql-data-compare/getting-better-performance-out-of-sql-data-compare

  11. ReadyRoll 1.16 release notes

    work again when pre or post scripts are readonly Improvements Do not write USE T-SQL statements between post deployment scripts when patc

    /rr1/release-notes-and-other-versions/readyroll-1-16-release-notes

  12. Data Population

    are easier to implement than others. Strategy A: Create and populate your databases from scratch using project sources This approach requ

    /rr1/key-concepts/data-population

  13. Migrations

    be written in the syntax of a T-SQL "IF" statement condition, for example: -- <Migration Id="{UniqueIdentifier}" Condition="@@SERVERNAME

    /rr1/key-concepts/migrations

  14. Options used in the command line

    triggers following deployment. DisableAndReenableDMLTriggers Alias: t Disables DML triggers on tables and views before deploying the data

    /sdc13/using-the-command-line/command-line-syntax/options-used-in-the-command-line

  15. Getting better performance out of SQL Data Compare

    a T-SQL WHERE clause in the box: image2016-9-1 11:5:19.png You can apply the same WHERE clause to multiple tables, by highlighting the re

    /sdc12/getting-more-from-sql-data-compare/getting-better-performance-out-of-sql-data-compare

  16. Options used in the command line

    deploying the databases, and re-enable those triggers following deployment. DisableAndReenableDMLTriggers Alias: t Disables DML triggers

    /sdc12/using-the-command-line/command-line-syntax/options-used-in-the-command-line

  17. Options used in the command line

    triggers following deployment. DisableAndReenableDMLTriggers Alias: t Disables DML triggers on tables and views before deploying the data

    /sdc15/using-the-command-line/command-line-syntax/options-used-in-the-command-line

  18. Getting better performance out of SQL Data Compare

    a T-SQL WHERE clause in the box: image2016-9-1 11:5:19.png You can apply the same WHERE clause to multiple tables, by highlighting the re

    /sdc15/getting-more-from-sql-data-compare/getting-better-performance-out-of-sql-data-compare

  19. How SQL Monitor works

    computers, via WMI, and it interrogates the SQL Server service conventionally using T-SQL via TDS. The WMI protocol used by SQL Monitor c

    /sm11/installation-and-setup/how-sql-monitor-works

  20. Restoring backups - destination database

    WITH REPLACE in a T-SQL RESTORE statement. Refer to your SQL Server documentation http://msdn2.microsoft.com/en-us/library/bb545450.aspx

    /sbu9/restoring/restoring-backups/restoring-backups-destination-database

  21. SQL Monitor 3.0 release notes

    own T-SQL queries to collect metric values that aren't currently collected by default. They can also be used to collect application-speci

    /sm12/release-notes-and-other-versions/sql-monitor-3-0-release-notes

  22. About Command Line Automation

    , specify this option for each schema. If not specified, all schemas that contain tables will be added to the masking set. -p, --parfile <

    /dms7/data-masker-help/general-topics/about-command-line-automation

  23. LCK_M_IX

    these metrics to see whether memory problems or I/O bottlenecks are causing locks to be held for longer than usual: Machine: memory used

    /sm12/sql-server-performance-and-activity-monitoring/dashboards-and-overviews/server-overview-pages/performance-diagnostics/top-waits/list-of-common-wait-types/lck_m_ix

  24. LCK_M_UIX

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

    /sm12/sql-server-performance-and-activity-monitoring/dashboards-and-overviews/server-overview-pages/performance-diagnostics/top-waits/list-of-common-wait-types/lck_m_uix

  25. LCK_M_SIX

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

    /sm12/sql-server-performance-and-activity-monitoring/dashboards-and-overviews/server-overview-pages/performance-diagnostics/top-waits/list-of-common-wait-types/lck_m_six


Didn't find what you were looking for?