There are people out there that reboot SQL Servers (or all servers) weekly. Usually the argument that I hear for doing this is that SQL Server has memory leaks which can only be resolved by rebooting Windows.
My argument against this, is that no SQL Server doesn’t have memory leaks which cause it to need to be rebooted weekly. SQL Server is designd to use all the RAM that’s allocated to it. By default SQL Server is configured to use 2147483647 MB of RAM, or all of the RAM in the server. You can and should be changing this setting to a lower number so that there is memory for Windows and anything else that’s installed on the box (anti-virus, SSIS packages, SSAS, etc.). The people that I typically see doing these server reboots, have been doing them for 15-20 years, typically because back then rebooting a server would fix a problem. It won’t anymore.
There are servers that are running SQL Server that have been up for months, or years without issue (I’m ignoring the fact that you aren’t patching SQL Server and Windows here). I’ve persoally seen boxes with pretty heavy workloads on them that have run for years without having to be rebooted.
SQL Server doesn’t have any memory leaks. It’s a world class product of Microsoft, that runs millions of databases (if not more) and makes Microsoft billions of dollars in revenue each year. Whatever memory leak you think there is in SQL Server, there’s probably isn’t. If you think there is, then contact CSS at Microsoft to report the issue as Microsoft needs to patch the problem.
The biggest problem that people will see if that the buffer pool is flushed when the SQL Server restarts, and this causes SQL Server to read all the data it needs from disk as there’s no data in RAM. This causes performance issues right after the restart of SQL Server.
If you’re restarting SQL Server because there’s some performance issues that “goes away” after a SQL Server restart, we’re going to be better off dealing with the root cause of what’s causing the problem to come up to begin with. It’s probably going to be indexing or statistics, but that’s just a guess as every server is different, but it’s probably a safe guess. Looking at the server will tell us what the problem is for sure, so we can solve the problem (and hopefully make the server faster in the process).
The post Should SQL Servers be rebooted weekly appeared first on SQL Server with Mr. Denny.
Today we are proud to announce that Denny Cherry & Associates Consulting is growing our team of consultants again. Our newest team member is Meagan Longoria from Denver, CO.
Meagan is a Microsoft Data Platform MVP living with her adorable dog Buster in Denver, Colorado. She is an experienced consultant who has worked in business intelligence, data warehousing, and database development for over ten years. She enjoys creating solutions in Azure and SQL Server that make data useful for decision makers. Her areas of expertise include data visualization, dimensional modeling, and data integration design patterns.
Meagan enjoys sharing her knowledge with the technical community by speaking at conferences, blogging at DataSavvy.me, and sharing tips and helpful links on twitter (@mmarie).
With the addition of Meagan our team of consultants now includes 5 Microsoft Data Platform MVPs, which is more MVPs than most large consulting companies have.
We’re thrilled to have Meagan joining our team.
The post DCAC Grows Again, Adding Meagan Longoria to our team of Excellent Consultants appeared first on SQL Server with Mr. Denny.
OCEANSIDE, Calif., Jan. 31, 2019 /PRNewswire/ — Today, Denny Cherry & Associates Consulting announced the hire of Microsoft veteran Peter Shire as Director of Sales.
Most recently Director of Data and Cloud Services with Aspire, Peter Shire began his career with an eight-year stint in Microsoft’s sales organization before moving on to several senior sales and marketing positions in the technology industry. In his eleven years at SentryOne as Director of Partner Relationships, Peter designed, built and managed the company’s highly successful Partner program, their relationship with Microsoft, and was responsible for a significant portions of the company’s annual revenue.
CEO and Principal of DCAC, Denny Cherry met Shire in his longtime role as President of the Charlotte SQL Server Users Group (CSSUG), where he has grown the organization into one of the nation’s leading users group.
Cherry commented, “I knew when I met Peter that he had the knowledge, skills and connections to be a great asset to DCAC, and I look forward to working with him. He’s extremely knowledgeable of Microsoft products, as well as negotiating with small and medium-sized enterprises, all which we urgently need as a high growth Microsoft Partner Company. He’s also simply a great guy personally. We couldn’t be prouder to have Peter joining our team.”
Shire responded, “I have known and admired Denny for almost ten years. His knowledge and comfort working with cutting edge technology in high pressure environments is elite level. And Denny’s long-term commitment to the Microsoft Data Platform community is unmatched and, in certain circles, even legendary. I have closely watched as he has grown DCAC adding respected experienced technologists one after another. I am confident there isn’t any engagement they couldn’t handle, and I am very excited to now be part of the DCAC team.”
About Denny Cherry & Associates Consulting
Award-winning Microsoft Partner and Gold Platform certified Denny Cherry and Associates Consulting assist companies with reliably attaining IT goals such as Azure Migration, HA, scalability, SQL Server virtualization and acceleration, while finding ways to save on costs. With clients ranging from Fortune 50 corporations to small businesses, their commitment to each is the same: to provide a deft, high-speed IT environment that maximizes every aspect of their platform: from architecture, to infrastructure, to network.
SOURCE Denny Cherry & Associates Consulting
When looking at support documents for Office365, you’ll often see instructions like “connect PowerShell to Office365,” but there are no instructions on how to do that. I was going through this, and thought, this is a problem I can fix. It only takes a few lines of PowerShell to connect your PowerShell to an Office365 environment. Basically what you are doing is PowerShell Remoting. The underlying code that you’ll want to run is this:
$UserCredential = Get-Credential
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection
Import-PSSession $Session -DisableNameChecking
When you run this code, it’ll prompt you for a username and password (that’s what the second line does). These are the credentials that you use to manage the Office365 environment. After that, you can fire off whatever commands you need to, and they’ll be send to the Office365 farm, and the response will be sent back to your PowerShell window.
It should be noted that you’ll get an error with the line that starts with “$Session” if you have MFA on your account. You’ll either need to disable MFA or put an exception for your IP address so that you don’t get an MFA prompt. Once you do that, you can authenticate without MFA, and the third line of the code will work as connectinos to Office 365 via PowerShell appear not to support MFA currently.
The post Connecting to Office365 with PowerShell appeared first on SQL Server with Mr. Denny.