I have some questions about this upgrade/migration that I can't seem to find via a web search. The area that causes us the most questions is the new database platform. My questions are:
It appears we have the option to not migrate to the new database platform. Does this mean that historical data doesn't have to be migrated, but in order to use 4.0 we must utilize the new platform no matter what? Basically, if we want this new product we have to use the new database?
If we can stay with SQL Server only, what are the consequences?
When historical data is migrated from SQL Server to the new database, does all of the existing data get ported or just some? I'm not clear if choosing to convert means that all data will now be stored on the new platform and after a successful port the SQL Server database is no longer used, or does NTA now use both the SQL Server AND the new platform as part of the upgrade?
Who will support a FastBit installation(s) at our Site? With SQL Server, it is clear what our responsibilities are with regards to backups, installation, maintenance and patches, etc. Does SolarWinds support this in the event of a problem as part of a standard maintenance agreement, does support for this require an additional agreement and cost? Is support even available via SolarWinds and we would possibly have to learn the hard way or engage a consultant? I need to know about how to backup, restore, tuning, etc.
Are there maintenance tools for this new database as they exist now for SQL Server? There are processes that reorganize indexes, etc. in the current product. While I don't really rely on them I wonder if there are similar processes in place for the new database? If not, is there a guide to this? Also, I see in the FAQ there is an item about what to do if the database runs out of space. The response was to lower the retention policy. Our retention policy is set per client and lowering this could very well violate the SLA. If the database needs more space (assuming the lack of space isn't disk related) can it be expanded on the fly? Is there any kind of documentation someone can point me to that covers the care and feeding of this new platform?
In the FAQ there are some tips about sizing the new database. I understand that these are suggestions, but I'm not clear on what, if anything, I need to plan for as far as growth. Suggestions?
In the SQL Server world we have standard practices regarding what type of files go on what type of RAID array. Is there any guidance for this new database?
Basically this new database has us concerned and for good reason. We know little about it and introducing it in a production environment has us nervous.