Now that you’ve setup your Azure account we can get started on building the test environment. First thing you should do is to create a Virtual Azure Network, this will be used for connectivity between your servers. Creating a Network is quite straightforward business. Choose Networks and then Create A Virtual Network.
Going back a few years (and then some), creating your own test environments used to be difficult requiring both time and hardware resources. Then came the different virtualization solutions, which made it bit more easier but still requiring decent amount of hardware resources and a little bit of time. With the arrival of Azure and other cloud-based solutions, things finally got considerably easier. Now we finally had the ability to set up a test environments quickly and easily.
I ran into and old issue recently I hadn’t seen in a while. A database server was experiencing some intermittent performance issues that didn’t make much sense. It didn’t take me long to figure out what was going on though, after firing up the Resource Monitor.
And so it is that PASS Summit 2013 has come to an end. And I have to say that for a first timer like me, it was truly an eye-opener to what SQL Server Community is all about. The quality of the sessions and the deep knowledge of SQL Server internals, virtualization and dozens of other subjects the speakers possessed was just astounding, but also expected.
I’ll hit the road and air (can you actually hit the air?) in a couple of days to start my journey towards Charlotte, North Carolina to attend the PASS Summit 2013. This will be my first time in the PASS main event of the year and I am quite excited that I got the company approval to go. I’ve previously attended one of the SQL Rally Nordic events, which was at Copenhagen last year, that was also a great experience and also one of the main reasons our company is now sending a group of five people to Charlotte.
In my previous post we took a quick look into one of the SQL Server features that I personally consider to be a great boon to any DBA, the Dynamic Management Views and Functions. Im going to show you through some basic examples on how you can use these views to get meaningful information out of your SQL Server instances.
I’ve been working with SQL Server ever since 1999, back then it was the 6.5 version which was soon replaced by the SQL Server 2000 (we skipped the 7.0 completely). Back in those days getting information out of SQL Server was much, much more difficult and you had way less tools for it. Then came the SQL Server 2005 and suddenly there was a plenty of information available to make troubleshooting and working on performance issues so much easier.
In fact there’s so much information available these days, that finding out where simply to start can be a daunting task. When I first started working with SQL Server 2005 my first task was to familiarize myself with the new feature called Dynamic Management Views and Functions, or DMV’s as they’re sometimes called. In SQL Server 2005 you have about 90 DMV’s, in SQL Server 2012 the number of DMV’s is almost 180. They’re definately an important tool in any DBA’s toolkit. And that is what this article is about, to get yourself started with the DMV’s.