For the second part of this series, I’m relying on a TSQL Code Smells Finder hosted on Codeplex. The solution consists out of 3 files (one PowerShell script, a text file containing a list with possible errors and a whitelist file) and build within PowerShell.
When moving a new SQL server database into production or taking over maintenance duties, you might want to perform some audit’s first. Audit reports make it easy to identify issues and rais additional questions.
I like to keep a close eye on my servers and users/customers. However, not want to do everything manually. This is not only very time consuming, but also most likely to find important issues rather late, hence the script below.
The SQL Server SMO client API can be used query and alter settings and objects within your SQL Server instances. In case you want to query your user database; you will run into some limitations. The client API isn’t aware of your data objects and, therefore, not exposing a typed scheme. Fortunately, it’s pretty easy to accomplish when using the SQL Server PowerShell Module (SQLPS)
I was addressing performance issues onsite just a couple of weeks ago. While waiting for the right authorizations, access tokens, and whatever you need nowadays just to run some scripts…, one of the developers approached me. They asked for some insights on how to Scripting SQL Server installations.
Validating database integrity regularly is a fundamental task that is often forgotten by the accidental DBA. Fortunately, SQL Server database corruption issues aren’t common. Finding out that you have been backing up a corrupt database for weeks might be somewhat hard to explain to the business.
Recently I had to move a couple of Windows Azures Virtual Machines from West Europe to Southeast Asia. This process wasn’t as easy as expected, so therefore I’m sharing the steps on how to move a Virtual Machine to a different data center.
Recent Comments