Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
Need connection string for SQL 2008.
Hello all,
I need a connection string from c# to SQL server 2008.
The code below doesn't work.
Provider = SQLOLEDB; Server = ServerName; User id = UserName; Password = ThePassword; Database = TheDB
I get Invalid connection string attribute
I'm using ADODB.
I need a connection string from c# to SQL server 2008.
The code below doesn't work.
Provider = SQLOLEDB; Server = ServerName; User id = UserName; Password = ThePassword; Database = TheDB
I get Invalid connection string attribute
I'm using ADODB.
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
I forget exactly what 2008 needed, but try this newer syntax:
»bp
"Provider=SQLOLEDB;Data Source=serverName;Initial Catalog=databaseName;User ID=MyUserID;Password=MyPassword;"
»bp
Well, that's connecting to it as a RDP server, not a SQL Server database server. It sounds like SQL Server may not be running there currently.
»bp
»bp
www.connectionstrings.com - The connection string bible as it were.
Specifically: https://www.connectionstrings.com/sql-server-2008/
Specifically: https://www.connectionstrings.com/sql-server-2008/
Make sure to not use spaces before =, and better not to do that after either.
Provider= SQLOLEDB; Server= ServerName; User id= UserName; Password= ThePassword; Database=TheDB
Just to be clear, web pages would come off of an IIS web server, not a SQL Server database server.
Both could be active on the same server, but just to clarify...
»bp
Both could be active on the same server, but just to clarify...
»bp
Right... I have a webserver that has SQL on it. What I'm trying to do is write a piece of software that monitors and email address. Once it sees an email it will parse it and update some fields in a SQL database.
Currently the program can pull the email and parse it.
What I thought would be a no brainer (connecting to SQL) is the most difficult part.
Currently the program can pull the email and parse it.
What I thought would be a no brainer (connecting to SQL) is the most difficult part.
Sheldon ... can you create a SQL Server ODBC connection to the SQL Server and see your databases in the wizard ?
Ok ... that means that SQL is not listening for connections (or cannot resolve the name).
Can you connect via IP address?
Can you TELNET <ip address> 1433 (assuming you're using the default SQL port)?
If not, you might want to start by rebooting the server (if you haven't already).
Can you connect via IP address?
Can you TELNET <ip address> 1433 (assuming you're using the default SQL port)?
If not, you might want to start by rebooting the server (if you haven't already).
I can RDP via the IP address... the local IP address (non-routed 10.x)
I'll need to install Telnet later.
Server is working fine and not needing a reboot. It is a webserver and is serving up pages fine.
I'll need to install Telnet later.
Server is working fine and not needing a reboot. It is a webserver and is serving up pages fine.
As Bill mentioned earlier, IIS and SQL Server are different services (IIS listens on 800/443, and SQL listens on 1433), so just because one is working, doesn't mean that the other is.
If you RDP to the server, can you connect to the databases with SQL Server Management Studio?
If you RDP to the server, can you connect to the databases with SQL Server Management Studio?
I would suggest installing TELNET on a PC and checking if you can TELNET via port 1433.
If you cannot, there may be a firewall blocking access.
Do you have Windows Firewall enabled on SQL Server?
It may not be configured to allow connections on port 1433 .
You might want to try turning it off temporarily to see if that makes a difference.
If you cannot, there may be a firewall blocking access.
Do you have Windows Firewall enabled on SQL Server?
It may not be configured to allow connections on port 1433 .
You might want to try turning it off temporarily to see if that makes a difference.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial