Posts by Chris Presley
Thanks to virtualization and cheap, powerful hardware there are a lot of cost effective options available today for setting up a learning environment on your own. In this blog post I will make suggestions on how you can cheaply build yourself an IT Playground, I’ll also talk about some mistakes I made along the way to hopefully save you from adding a few grey hairs.
Continuing on from my last post, I felt like cleaning up some more data and using more SQL Server 2012 features. I happened on DATEFROMPARTS on MSDN and felt like playing with it.
One new feature in SQL 2012 that I am very excited about is TRY_CONVERT which makes data conversion much easier. When you pair TRY_CONVERT with some Case statements you can easily pipe the inconvertible data to other columns which can then be reviewed and (hopefully) fixed prior to cutting over your data. I’ve mocked up a quick demo so you can see how powerful this new feature is.
I’d read that DTS packages could be stored on SQL Server 2005 64-bit, but not executed on this server. Workarounds I’ve seen range from creating SSIS packages with Execute DTS tasks, migrations to SSIS using the wizard or third party tools, and running the DTS Packages from a 32-bit server against the 64-bit target. Recently (and much to my embarrassment after making that statement), a colleague demonstrated that this is not correct.
This is the first post in a series dedicated to exploring the backup and availability options in SQL Server 2005 and 2008. It is aimed at anyone unfamiliar with the database backup options in SQL Server 2005 and 2008. I’m not going to explore every single option or scenario, the goal is to give you the language and the tools to do deep dives where you need to.
Using OLE DB to get SQL Server to connect to Oracle servers can be done quite easily, but there are a few little tricks you should know to make it go smoothly. Once it’s working it seems to work quite well. I hope this blog post will save you a few headaches.
Let’s say for you want to move a database from one environment (possibly production) to another (possibly development) on a semi-regular basis. After about the 10th time doing it manually, you’re ready to automate the process. But how? That’s what I intend to help with in this post. There are a couple ways you could go about this task. One way would be to write stored procedures and call them with a batch file using osql.exe and SQL Agent job or your enterprise scheduler. There’s nothing wrong with that approach, but I think that for this task, SSIS packages give more options, flexibility, and simplicity for ongoing management.
Have you ever used Perfmon to collect performance statistics about a particular Windows Server? Do you hate manually picking the counters out of the list? Do you trace basically the same counters every time? If you answered “yes” to any of these questions, here’s a tip that can save you some time.
I’m going to write a small series of posts on this server virtualization because its something that will affect a lot of us even if you aren’t a DBA. I’m starting at the very beginning, so if you’ve already created virtual templates for all of your core applications, this post won’t have anything new for you. If you’re wondering what about “virtual” is virtual, this is the post for you to start at.