I cant believe the lack of customer consideration in forcibly upgrading all our SQL Server DBs from 2008 to 2012, and the legacy maintenance issues and work it is now causing us.
Arvixes only email warning was on 5th Aug 2103, foloweed by on 2 days later saying it was all finished. GULP! I am so busy I dont usually even get a chance to properly catch up with all my weeks emails till the next weekend. Thats no warning at all, nor any choice? It didnt even give us sufficient time to take fresh backups.
So now the only backups we can get are SQL Server 2012, which cant be restored to SQL Server 2008 to work on offline. How do we fix a production issue if one was to occur right now
The response I got from your support staff was
1) to go out and buy SQL Server 2012 ($4,000 for Standard Edition) and
2) sales spin about how much better it is.
It felt like I was talking with Microsofts marketing dept.
Question: Is your hosting service aimed at hobbyists? Or at commercial applications were migrations to newer versions of tools needs to be agreed and planned by all affected? Some aren't even just up to us, the developers, they have to include our paying customers with SLAs.
We have at least one live database used by customers that is subject to being auditable under financial laws that we now cant restore offline to SQL Server 2008 at all.
Any professional developer knows, you do NOT work against your live DB. You work against an offline copy in isolation. What if we had a problem with that right? How would we get a copy we could restore to SQL Server 2008 to investigate?
I have worked as a professional .Net and SQL Server developer for many many years, and no commercial organisation would just upgrade DBs on existing live commercial applications without it being planned and co-ordinated well in advance with at minimum the developers.
SQL Server 2008 and 2012 can co-exist. You could have left 2008 there and only upgraded those who had applications that they were ready to have migrated.
We are now going to be FORCED by Arvixe to have to get SQL Server 2012 and will have to spend the next few weeks trying to change all our development environments and tools over to use SQL Server 2012.
This is one of the reasons we left our last hosting company. A complete disregard for the impact these sort of changes have on customers. When applications are live it is NOT just about the new shiny functionality in development tools.