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

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

  1. Tutorial - Java-based Migrations

    | +-----------+---------+---------------------+------+---------------------+---------+ Note the new pending migration of type JDBC. Execu

    /fd/tutorial-java-based-migrations-184127624.html

  2. Refreshing Triggers stored in the masking set

    , but what if there are? 3. Go back to the Rules in Set tab and Edit the Rule Controller, select the Tools tab and within it click Refresh

    /dms6/data-masker-help/version-6-tech-tips/refreshing-triggers-stored-in-the-masking-set

  3. Windows monitoring - WMI connections

    over WinRM, go to: WMI over WinRM https://documentation.red-gate.com/display/SM13/WMI+over+WinRM. If using WMI over DCOM, go to: WMI over

    /sm13/windows-monitoring-wmi-connections-199100084.html

  4. Licensing Your Servers

    Go to the Licensing page by doing one of the following: Click on the Enter serial number link in the top right corner of the page: enter-

    /sm9/configuring-sql-monitor/licensing-your-servers

  5. Adding servers to monitor

    . See Supported platforms for a list of supported servers. Go to the Configuration tab and under Monitoring, select Monitored servers. Cli

    /sm9/configuring-sql-monitor/adding-servers-to-monitor

  6. Monitoring SQL Server Failover Cluster Instances and AlwaysOn Availability Groups hosted in Azure IAAS

    to query WMI. The choice you make determines the port that will be used in the following instructions. If you are going to use DCOM, the

    /sm9/configuring-sql-monitor/adding-servers-to-monitor/monitoring-sql-server-failover-cluster-instances-and-alwayson-availability-groups-hosted-in-azure-iaas

  7. Troubleshooting SharePoint profiling

    administrator's account. Open a command prompt and run: gpupdate /force to enforce the new settings. Open Administrative Tools and go to

    /amp/troubleshooting/common-issues/troubleshooting-sharepoint-profiling

  8. Customizing the alert settings

    of creating and configuring those. Changing the default settings (the All Servers level) for each alert type Go to the Configuration page

    /monitor14/customizing-the-alert-settings-239667920.html

  9. SQL Monitor 10 Documentation

    on "bare metal" servers, in Virtual Machines, or in the cloud. For more information, or to download SQL Monitor, go to the SQL Monitor pr

    /sm10

  10. Preparing to upgrade SQL Monitor

    licenses, you can add the support and upgrades package to make upgrading easier. To find your serial numbers, go to http://www.red-gate.c

    /sm10/maintaining-and-upgrading-sql-monitor/upgrading-sql-monitor/preparing-to-upgrade-sql-monitor

  11. Can't connect to Active Directory authentication service

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

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

  12. Rewinding time with Back in Time mode

    need to go further back in time to a previous day, week or month: Click the date/time. The date picker is displayed with today's date sel

    /sm10/sql-server-performance-and-activity-monitoring/dashboards-and-overviews/server-overview-pages/activity-graph-and-snapshot-metrics/rewinding-time-with-back-in-time-mode

  13. Using Azure Interactive Authentication

    URI. image2021-12-6_13-32-52.png Go to Add a platform > Mobile and desktop applications and then ensure

    /fd/using-azure-interactive-authentication-138347162.html

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

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

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

    /soc5/configuring/disable-tfs-policy-checking

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

    /soc5/configuring/move-the-working-base

  17. Upgrading from old versions of migration scripts

    : In the SQL Source Control window, go to the Commit tab. Using the checkboxes, select all existing migration scripts. Enter a comment for

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

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

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

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

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

  20. Troubleshooting the SQL Comparison SDK

    and delete licenses.licx, then go back into the project, right-click, add new, file, call it licenses.licx. Check the properties of licen

    /rp/sql-comparison-sdk/sql-comparison-sdk-12-documentation/troubleshooting/troubleshooting-the-sql-comparison-sdk

  21. Excluding tables which are no longer required in your masking set

    and edit the Rule Controller. Go to the Tools tab and Refresh Tables and Indexes: DMS6_doc7_img2.png The odds are very good that more tab

    /dms7/data-masker-help/tech-tips/excluding-tables-which-are-no-longer-required-in-your-masking-set

  22. SOS_SCHEDULER_YIELD

    exhausted their quantum will voluntarily yield to give the next thread in the runnable queue its CPU time. Yielded threads don’t go on th

    /sm11/sql-server-performance-and-activity-monitoring/dashboards-and-overviews/server-overview-pages/performance-diagnostics-queries-and-waits/top-10-waits/list-of-common-wait-types/sos_scheduler_yield

  23. OLEDB

    be caused by: Remote procedure calls set up within a query. BULK INSERT commands that go through OLEDB calls. Using full text search, or

    /sm11/sql-server-performance-and-activity-monitoring/dashboards-and-overviews/server-overview-pages/performance-diagnostics-queries-and-waits/top-10-waits/list-of-common-wait-types/oledb

  24. Configuring a VMWare host then adding the Virtual Machine

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

    /sm11/adding-and-managing-monitored-servers/adding-servers-for-monitoring/configuring-a-vmware-host-then-adding-the-virtual-machine

  25. Moving the SQL Monitor database

    If you want to move the SQL Monitor database (also called the Data Repository), follow these steps: Stop the Base Monitor service. To do

    /sm11/maintaining-and-upgrading-sql-monitor/maintaining-sql-monitor/moving-the-sql-monitor-database


Didn't find what you were looking for?