February 26, 2009 at 3:52 pm
Im using a CLR I built in C# and installed on SQL Server 2005. When I execute the CLR on my laptop it works great but when I try to execute if from a server it gets the above error.
I'm using the following connection string: Provider=MSOLAP.3;Data Source=**Server Name**\sql2005_3;User ID='''';Initial Catalog=**DatabaseName**; Cache Authentication=False;'
Does anyone have a clue how to fix this issue?
February 26, 2009 at 6:40 pm
What are you doing in CLR and why aren't you using the context connection? Looking at your connectionstring, your password is missing. We need to know more about what you are trying to do to give you better ideas of where to look. Using a non-context connection requires UNSAFE Assembly rights, which is not recommended. If you need to call another SQL Server, try a linked server, or consider moving this outside of SQL Server and using a SqlDependency to activate an external service in C# to perform the tasks needing done. Service Broker is extremely powerful for creating distributed database operations. It is very likely that you are using the wrong tool to solve whatever problem you have.
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
February 27, 2009 at 10:42 am
Thanks for your comments.
We are using this CLR to read data from Analysis Services cubes and write that data into a conventional table. We built the tool so that all it needed was a Analysis Services connection string, an MDX query string and a table creation string. The idea was to build a tool that can be used in many applications with minimal configuration.
Is there a more appropriate tool or better methodology to use? This is new ground for me so any advice is helpful.
February 27, 2009 at 10:44 am
Is this a SQLCLR stored procedure, or an external application to SQL Server?
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
February 27, 2009 at 10:48 am
The CLR is written in C# and compiled as a dll.
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply