How can we help you today? How can we help you today?
philljones22

Activity overview

Latest activity by philljones22

NYT Sudoku Medium puzzles are ideal for those seeking a balanced challenge that sharpens both logic and strategy. With grids that are more engaging than the easy level, they offer just the right amount of complexity to keep you focused / comments
NYT Sudoku Medium puzzles are ideal for those seeking a balanced challenge that sharpens both logic and strategy. With grids that are more engaging than the easy level, they offer just the right am...
0 votes
To compare two databases for differences in collations, you can use one of the following methods: 1. Querying System Views in SQL Server You can query system catalog views such as INFORMATION_SCHEMA.COLUMNS or sys.columns to check the collation for each column in your databases. For example: -- For Database 1 USE [Database1]; SELECT TABLE_NAME, COLUMN_NAME, COLLATION_NAME FROM INFORMATION_SCHEMA.COLUMNS WHERE COLLATION_NAME IS NOT NULL; -- For Database 2 USE [Database2]; SELECT TABLE_NAME, COLUMN_NAME, COLLATION_NAME FROM INFORMATION_SCHEMA.COLUMNS WHERE COLLATION_NAME IS NOT NULL; Export these results and compare them using a tool like Excel or a diff utility. 2. Third-Party Tools Tools like SQL Compare (from Redgate) or ApexSQL Diff allow you to compare databases, including schema and collation differences, in a user-friendly interface. 3. Custom Script for Automation Write a custom script in T-SQL or PowerShell that connects to both databases, retrieves collation information, and compares them programmatically. 4. Manual Inspection in SSMS Using SQL Server Management Studio (SSMS), navigate to: Database > Tables > Columns Right-click a column > Properties > Collation While this method works, it can be time-consuming for large databases. To get the more information about latest trends, info and tech visit influencersgone wild. / comments
To compare two databases for differences in collations, you can use one of the following methods: 1. Querying System Views in SQL Server You can query system catalog views such as INFORMATION_SCHE...
0 votes
The "Interval Processor CPU %" column in SQL Monitor’s "SQL User Processes (Top 10 by CPU)" section represents the percentage of CPU usage attributed to each process during the interval monitored. Here's what it means and how to interpret it: 1. Meaning of the Metric:      This column shows the proportion of the total CPU capacity consumed by the specific SQL user process during the interval being analyzed. A value of 97%+ indicates that these processes are heavily utilizing the CPU, suggesting significant load or potentially inefficient queries. 2. Understanding the Interval:      The interval refers to the timeframe over which CPU usage is averaged or captured. Typically, this is a snapshot of activity during a configured period (e.g., 5 or 10 seconds). This metric helps identify which processes are consuming the most CPU resources in real time or over short durations. 3. Documentation:      While Redgate, the maker of SQL Monitor, provides documentation on its performance metrics, the specifics of "Interval Processor CPU %" are often contextually explained in performance tuning guides. Look for detailed Redgate SQL Monitor documentation or SQL Server diagnostic references on interpreting CPU usage. 4. Next Steps:      If all processes show 97%+ CPU usage, your server might be under heavy load. Investigate the queries causing the load:    Check for inefficient queries using the execution plans.    Identify long-running or CPU-intensive queries.    Optimize indexes or resource allocation as necessary. For more tailored details, consult the Redgate SQL Monitor documentation or explore the tool's support forums for specific examples. For more information visit: https://influlencergonewild.net/. / comments
The "Interval Processor CPU %" column in SQL Monitor’s "SQL User Processes (Top 10 by CPU)" section represents the percentage of CPU usage attributed to each process during the interval monitored. ...
0 votes
To resolve the connection string errors you encountered, you adjusted the `ShadowConnectionString` configuration in a specific sequence. Here’s a summary of the process and the final configuration that worked: 1. **Initial Error:**    You encountered an error indicating that the keyword `Trust Server Certificate` was not supported.        ```    Keyword not supported: 'trust server certificate'.    ``` 2. **Attempted Fix:**    You removed `Trust Server Certificate=True`, which led to a new error regarding `Multi Subnet Failover`.    ```    Invalid connection string: Keyword not supported: 'multi subnet failover'.    ``` 3. **Subsequent Error:**    Removing `Multi Subnet Failover=False` resulted in an SSL-related error during the login process.    ```    Error connecting to database: A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.)    ``` 4. **Final Adjustment:**    Based on the solution found on StackOverflow, you added `Trust Server Certificate=True` back to the connection string, ensuring it was placed at the end of the `ShadowConnectionString` section. ### Final Connection String Here is the final, corrected `ShadowConnectionString` that resolved the errors: ```xml <ShadowConnectionString>Data Source=ip;Initial Catalog=Chuck2_Connect5;User ID=clu;Password=;Pooling=False;Encrypt=False;Authentication=SqlPassword;TrustServerCertificate=True</ShadowConnectionString> ``` ### Explanation of Changes - **Trust Server Certificate=True**: This parameter tells the client to trust the server's SSL certificate without validating it. This resolves the SSL Provider error regarding the certificate chain being issued by an authority that is not trusted.    - **Placement and Formatting**: By placing `Trust Server Certificate=True` at the end of the connection string and ensuring correct formatting (no spaces within the keyword), the connection string is interpreted correctly by the connection manager. ### Conclusion These adjustments resolved the connection issues by instructing the system to trust the server certificate and removing unsupported keywords. This ensures a successful and secure connection to the database. / comments
To resolve the connection string errors you encountered, you adjusted the `ShadowConnectionString` configuration in a specific sequence. Here’s a summary of the process and the final configuration ...
0 votes