Register Developer regular Mark Whitehorn is rolling out a significant new IT project. This has, at its heart, a database of around 1TB and is ultimately expected to support several thousand users.
The project is using nothing less than upgrades to a trio of big-ticket products from Microsoft – Visual Studio 2008, Windows Server 2008, and SQL Server 2008 – that are due next month. With Reg Dev, Mark will chart his experiences and record his frustrations during deployment of these major updates.
Over to Mark who, this week, sets the scene…
Experience has taught database people to be very, very conservative. Actually, it’s more like a selection thing. There are old DBAs and there are bold DBAs, but there are no old, bold DBAs.
If an application runs fine on version eight of your preferred RDBMS, why would you even consider upgrading to version nine? The best you can possibly hope for is that it continues to run fine (no gain there then); the worst is crash, burn and time to find a new job elsewhere. This is why we have production systems still running in COBOL.
Our current database is running on SQL Server 2005, sitting on Windows Server 2003. We are also using Analysis Server 2005 to produce the OLAP cubes and ProClarity for the data visualization. It works. So why am I sitting here, two months shy of the launch of SQL Server 2008, Windows Server 2008 and Visual Studio 2008, desperately seeking servers that will run this entire 2008 stack and porting an application that will go live (for a subset of the users) long before the summer?
Microsoft, Windows Server 2008, WS 2008, Stack, Article