Managed service contracts are great - when they're making you money. Yes, you’re getting paid monthly, but is it actually profitable? Learn to calculate your hourly overhead burden so you can master your IT services pricing strategy.
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.
Who is Participating?
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get this solution by purchasing an Individual license!
Start your 7-day free trial.
I wear a lot of hats...
"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.
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.
Experts Exchange Solution brought to you by
Your issues matter to us.
Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.
Start your 7-day free trial
So... I shut down the FW and could connect. I then turned on the FW and made an inbound rule for 1433 and it worked.
Thank you Sam!
Thank you Sam!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SQL
From novice to tech pro — start learning today.
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get this solution by purchasing an Individual license!
Start your 7-day free trial.
Open in new window
»bp