April 30, 2013 at 7:21 am
I am requesting that the Microsoft Access Database Engine 2010 Redistributable be installed on my SQL 2008R2 Enterprise SP1 running on Windows Server Enterprise 2008R2 SP1 but am getting denied the request because in the page to download the drivers (http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=13255) it states that:
The Access Database Engine 2010 Redistributable is not intended:
4.To be used by a system service or server-side program where the code will run under a system account, or will deal with multiple users identities concurrently, or is highly reentrant and expects stateless behavior. Examples would include a program that is run from task scheduler when no user is logged in, or a program called from server-side web application such as ASP.NET, or a distributed component running under COM+ services.
The requirement is to be able to run an SSIS package that interrogates various MS Excel 2010 workbooks before converting them to csv. The conversion to csv is just a side line so please do not be distracted by that, rather focus on the need to be able to look at the excel tables and other content. The package should run on a SQL Agent job through a proxy and credential with the credential running under the context of a service account that itself will have very limited privilege however it maybe that the package will reside on the server as a physical file and executed directly from a front end under a regular user.
Now because of this 'not intended' wording on the MS site my WINTEL support guys are denying my request but I have not been able to get any further information from them or in fact any where else as to why MS state this or what the issues might be. I just want a driver to be able to not just import from Excel but to dig deeper into the Excel file.
Does anyone know why this driver set should not be installed or why MS make this statement.
Thanks...
May 1, 2013 at 7:34 am
The "Additional Information" section of that KB seems to indicate that the use of that driver IS supported for SSIS.
May 2, 2013 at 9:37 pm
Get them to spin up a small VM on some other server and install it there. It won't hurt your process and should sooth them. Just don't mention the other things Microsoft has said, like "Access is the communications system of the future" (before they binned it and re-used the name for a rushed-to-market part of their Cirrus database project. Or maybe like "the Zune music system is here to stay" txtPost_CommentEmoticon(':-)');
May 3, 2013 at 2:51 am
Trust me if it were only that simple. I have made such suggestions on proof of concept type stuff and I'll load it up and push and stretch the trial box but I am working with administrators who a little way away from top tier and this appears to be a foreign concept to them. Even if I were to undertake such a trial and prove that no issues occur they would still not apply the change to any server due to this wording on the MS site. I appreciate the reply though.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply