Do i need to install sql server client tools connectivity

In the past, IвЂ™ve seen clunky login scripts cause an even larger impact.ДЄnother reason is that SSMS is a resource hog. On one (random) server I looked at, I could reliably see one CPU core bounce to 100% for almost a minute. If you watch Task Manager (or your monitoring software) while a user logs in via RDP, the CPU spike can be noticeable, particularly on a smaller server.

Establishing your session & running your login scripts from Active Directory will cause a memory & CPU spike. There are a bunch of reasons, but lets hit a few of the bigger/fundamental ones.ДЇirstly, just logging in via RDP can cause a pretty decent resource spike. If you have processes that involve вЂњLog in to the server via RDPвЂ¦вЂќ you should keep track of those processes, and revisit them so that you can eliminate the need to RDP to the server directly. My goal is to only use SSMS on the server if thereвЂ™s an emergency.ДЄll your normal processes should be things that you can do from your desktop, or from a central management server. If you find you have any operational tasks where youвЂ™re logging in to the server to use SSMS locally as standard operating procedure, reconsider your process. SSMS should be on your servers for an emergency, not for every day use. My advice is still: DonвЂ™t use SSMS on your servers SSMS is still the tool I need in an emergencyвЂ“at least for now.Д«ut thereвЂ™s a catch. Azure Data Studio and I are building our relationship, but thereвЂ™s still some work to do before it can be my DBA daily driver. In some cases, PowerShell is the tool of choiceвЂ“but not always. IвЂ™ve been using it for 15 years, and just about everything I need to do during a critical response will be fastest if I do it in SSMS. Every single one of the situations I list above are scenarios that have happened to me in real life over the years, and every time, having SSMS on the server saved my bacon. At most of the jobs IвЂ™ve had over my career, having the fastest possible resolution to downtime is extremely important. In all those situations, your fastest response to fix the problem might be to RDP directly to the server.

Or maybe youвЂ™re on an airplane trying to fix a problem from 30,000 feet on a low bandwidth connection and SSMS pulls back too much data over that network connection. Maybe Kerberos is refusing connections because of SPN issues. Maybe the server got knocked off the domain and youвЂ™re having auth issues. Eventually, youвЂ™re going to have an emergency situation where the server is in trouble, you need to respond, and connecting remotely is problematic. Stop saying вЂњbest practiceвЂќ and get to the pointвЂќ However, thatвЂ™s actually a proposed solution to a best practice, rather than being itself a best practice. The pseudo best practice of вЂњdonвЂ™t install SSMSвЂќ is a misguided oneвЂ“advice that I even fell into repeating in the past. This came up at work recently, where I was asked вЂњShould we install SSMS on our database servers?вЂќ and my answer is: 1000%! Heck Yes. ThereвЂ™s a lot of advice out there on the internet that suggests that you should not install SSMS on your database servers running SQL Server.

Do i need to install sql server client tools connectivity