February 23, 2010 at 3:32 pm
bran, spankin new to 2005
trying to establish my first cx.
environment is classic asp, IIS6, W2003
I haven't molested the 2000 cx string, just made sure everything and everyone is known to 2005.
MAIS is the db within MSSQL2005
MAIS is the name of the MSSQL2005 server
MAIS is the name of the W2003 IIS web-site
Can anyone direct me or otherwise correct the following string(s):
Provider=SQLOLEDB.1;Integrated Security=SSPI;UID=webMAISuser;pw=userMAISweb;Persist Security Info=False;Use procedure for prepare=1;Auto Translate=True;Packet Size=4096;Initial Catalog=MAIS;Data Source=MAIS
the URL:
yields:
Microsoft OLE DB Provider for SQL Server error '80004005'
Invalid connection string attribute
==============
adding Server=MAIS; to the cx string
yields:
Microsoft OLE DB Provider for SQL Server error '80004005'
Cannot open database "MAIS" requested by the login. The login failed.
Both errors I've seen before and I've always been able to resolve them.
The Server parm is something I turned up trying to suss the differences but still not enough.
in 2000 webMAISuser had nothing special except PUBLIC role which is default now anyway.
in 2000 " is a standard user in security and I've confirmed the pw.
thanks, I hope someone can help, B
March 19, 2010 at 9:35 am
if using integrated security you'll not supply a UID and PW as those are passed through via your workstation login credentials back to the domain. Use UID and PW if instead using SQL Authentication.
- Tim Ford, SQL Server MVPhttp://www.sqlcruise.comhttp://www.thesqlagentman.com http://www.linkedin.com/in/timothyford
March 19, 2010 at 11:01 am
You cannot use both Windows Integration and SQL Authentication. Chose one or the other. And get rid of some of that other junk as well. Keep things simple.
All that you really need is a login, database name and server name. That is it.
Andrew SQLDBA
March 19, 2010 at 11:40 am
I don't remember exactly what it was -- it may have bben a rights issue elsewhere.
Heres the string I used:
"Provider=SQLOLEDB.1;Server=<sn>;Integrated Security=SSPI;Persist Security Info=False;User ID=<sqlid>;password=<sqlidpw>;use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Initial Catalog=<dbname>;Data Source=<dbname>"
note in this particular install <sn> & <dbname> are equal.
March 19, 2010 at 11:49 am
This is all that you need:
"Provider=SQLOLEDB;Data Source=<Your_Server_Name>;Initial Catalog=<Your_Database_Name>;UserId=<Your_Username>;Password=<Your_Password>;"
That is it, not good to have more than that.
Andrew SQLDBA
March 20, 2010 at 2:51 pm
AndrewSQLDBA (3/19/2010)
That is it, not good to have more than that.
Unless it is needed 😉
Failover partners spring to mind.
This site is pretty good:
http://www.connectionstrings.com/sql-server-2005
...as is Books Online of course.
Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply