SQL 2005
18 TopicsEffectively troubleshoot latency in SQL Server Transactional replication: Part 1
Are you struggling with latency issues in SQL Server Transactional replication? This article provides clear, step-by-step instructions to effectively troubleshoot and resolve these challenges. Dive into proven techniques and best practices that will help you enhance your SQL Server's performance and ensure seamless data replication. Don't let latency slow you down—master the art of SQL Server troubleshooting today! I hope you find this teaser engaging! If you need any adjustments or additional content, feel free to let me know. Thanks to Collin Benkler, Senior Escalation Engineer in Microsoft for SQL Server for his valuable feedbacks.4.4KViews3likes3Comments"Unsupported IIS Security Modes for Report Server" failed When you try to upgrade SQL 2005 to 2014
Issue Background: ======= Customer is running SQL Server 2005(X64) on Windows Server 2008, and they want to upgrade to SQL Server 2014 with in-place(can't accept side by side). But during the upgrading, the following rules are failed, this is related to Reporting Service, but actually customer never use it. Rule "Unsupported IIS Security Modes for Report Server" failed. Rule "Unsupported IIS Security Modes for Report Manager" failed. Rule "Client Certificate Required for Report Server" failed. Rule "Client Certificate Required for Report Manager" failed. Troubleshooting Steps: ======== 1. As this related to SSRS, so check if we can ignore the SSRS service only upgrade the other SQL service, but we can't change the feature to be upgraded. http://download.microsoft.com/download/7/1/5/715BDFA7-51B6-4D7B-AF17-61E78C7E538F/SQL_Server_2014_Upgrade_technical_guide.pdf 2. And then discussed with customer about the side by side upgrading, but they can't accept. 3. Suggest customer to upgrade the OS first, but we also can't make sure this will 100% work. 4. Then we go back to the error itself, this is related to IIS. So I open up Server Manager, and check IIS related service, WAS and W3SVC already running, but we saw IIS Admin Service is stopped. 5.We go to Services.msc and then set the Startup type to Manual and then start this “IIS Admin Service”, and then after re-run the rule, all rules are passed. 6. And then we continue Upgrading, after a while, upgrade completed without any other issue, Solution: ====== GO to Server Manager, and check IIS related service, make sure IIS related service is up and running, especially for WAS/W3SVC/IIS Admin Service.2.2KViews1like0CommentsSQL Server 2005 Setup Failure (Multi-Core, Tri-Core, …)
First published on MSDN on Jun 09, 2009 SQL Server 2005 has a startup check that fails on some of the newer CPU socket designs (triple core, tri core, 12 core, …) as outlined in the knowledge base article: http://support.394Views0likes0Comments