I’ve been using Powershell more and more lately, most of the time the motivation has been to do repeatable tasks much more quickly and efficiently but there has also been other cases where Powershell has been the only way to accomplish something. Most often this is due to lacking GUI or Windows issues that have prevented me from using the GUI in the first place. This post describes the latter scenario and the Powershell workaround.
Distributed Replay is a feature that was first introduced with SQL Server 2012. It allows you to play a set of recorded transactions against a SQL Server database. This can be extremely useful if you’re doing hardware or SQL Server version upgrades and want to test the performance impacts of these changes, or if they’re going to break your application.
Just finished watching the Data Driven event that was broadcasted live from New York earlier today. As expected there was a lot of information about SQL Server 2016 and quite a few visitors telling how their companies used Microsoft SQL Server in their daily business. And these were some big businesses, having impressive amounts of data and transactions to handle. With SQL Server 2016 Microsoft is giving us a feature packed and complete data platform to work with.
Not a long ago I was doing a database cluster delivery to one of our customers and as a part of that process, I scheduled our regular set of test runs for the storage. The results of the tests we ran were bad and none of the changes we did at the SAN weren’t helping. After a while we figured out that the issue was not in the test software or at the SAN but in the scheduled tasks we used to run the different test!
One of the more important duties of a DBA is to make sure that their databases and the data is secure. In this post we’ll be looking at two utilities to increase the security of your server, the Windows Firewall and an antivirus software. Like with about everything else related to servers, you can’t just switch these on (well, you could, but…) and forget about them to get the best possible experience. They need to be properly configured for servers running Microsoft SQL Server. If you’re a DBA you might not be doing the configuration yourself, but you still need to tell your Windows administrators what they need to do.
Changing options for multiple databases can be time-consuming when done one database at the time. With just few databases you might be fine using the Management Studio and doing changes through the GUI but when you have dozens, or hundreds, of databases and only some of them are having wrong options (like that stupid AUTO_CLOSE one) you need to replace, you’re going to want to use scripts for it.
This post comes a bit late as our last day in Seattle went on bit longer than expected, but for very positive reasons. We had an ad hoc gathering of Finnish PASS Summit attendees and despite the fact that it was very last minute setup, we got pretty much everyone there. The evening itself was hosted by Marko Hotti, one of the Senior Product Managers at Microsoft who moved to Seattle a while back and is now working on the SQL Server 2016 release. And while there was some (or a lot) talk about SQL Server and the PASS community, we did also get to relax bit after a long week.