Hello everybody,
Long-time reader, first time writer ;-).
We have been analyzing our SQL environment with our vendor and wanted to reach out to the community to ask for advice. Our main solution takes in large files daily and performs a series of logic that requires heavy writes to the disk upon import -- BCP or SSIS is not an option. We have a bare metal SQL server that is configured which handles the import of the largest files in three hours. We are looking to possibly use virtualization and SQL 2014 to provide a better disaster recovery option.
We are working through a proof of concept with our hosting provider that has SQL running in a VMWare virtual environment using SAN disk as the main disk. During our tests, the file that takes three hours to import takes around six hours in the virtual environment. Their engineers are looking at speeding up the SAN, but I would like to have an alternative.
Could I do something similar to the following: have a bare metal server act as the main import server, and then replicate the data to servers that are virtualized? I believe there is an always on feature with SQL 2014 which would provide automatic switch over in case of failure. How would you suggest I configure my environment to handle this? Would it be make sense to have the bare metal server kick off a Tlog transfer after the file is imported to the virtualized environment? If so, how would that look?
Thank you very much, in advance, for you advice!!!!!