Trouble connecting to an SQL database when using a table generator.
Updated: 21 May 2010 | 5 comments
This issue has been solved. See solution.
Here we go again. I began creating a new integration library to read info from an SQL database. I chose table generator, SQL server provider, and filled in the connection string using "Data Source=(local);Initial Catalog=myDatabaseName;User ID=myUsername;Password=myPassword;". It looks like it is finding the SQL server, but it is not allowing me to log on. I am able to log on and view the desired database in SQL server express. I've tried with and without the domain\user_name format, and also tried putting in the full path to the database (SQLSERVER\DATABASES\desired database). If it's not one thing, it's another. -Thanks.
discussion Filed Under:
Comments
local user
So I ran into this recently as well. If you're using a connection string like this, you CANNOT use a domain user account/password, it must be a local SQL account. It is a SQL server limitation, not a Workflow limitation. I think it may be that you need to use some different options in the string (maybe the IntegratedSecurity= part) because it seems fairly ridiculous that you can't use a domain account for this. But, from what I've seen with my limited exposure, that is the only way.
Thanks,
Kyle
Symantec Trusted Advisor
For Forum threads, please click "Mark as Solution" if answered.
For all content, please give a thumbs up if you agree with or support the post.
You're right, that is
You're right, that is quite rediculous. So you're saying that there needs to be a local account on the SQL server in order for WF to connect to the DB? Thanks again for all the assistance.
That's what I've found
That's what I've found in my brief time using WF. There may be a way to get the WF process running as a particular domain user, then use a trusted connection to the SQL server, i.e. "Logged on user", or the context the WF is running in, but I'm not sure of how to do that.
Thanks,
Kyle
Symantec Trusted Advisor
For Forum threads, please click "Mark as Solution" if answered.
For all content, please give a thumbs up if you agree with or support the post.
A solution...kind of...but not really
Well, I've found somewhat of a aolution, but the catch is that I believe whover is logged in and using the finshed, published project, will need to be granted access to pertinent DB.
Using
This works, but it only works if the account with which you are logged in has the appropriate permissions.
The previously mentioned
The previously mentioned connection string is actually what I needed anyway, since the only people that will be using this workflow are people that should have access to the SQL DB anyway.
Would you like to reply?
Login or Register to post your comment.