ambiguity of Connection strings of SQLServer And MySQL ? there's same providers ... help guys

Question

2.00/5 (2 votes)

See more:

There's ambiguity here :

the following connection strings :

MySQL

server = ip; database = dbname; uid= username; pwd=password;

now if i change:

server to data source it works.
database to initial catalog it works.
uid to user id or to username it works.
pwd to password it works.

So its now looks like SQL Server connection string ? why that ambiguity between them ?? and whats difference between using server or data source keywords ??

someone tell me please is there any benefits of using ambiguity keywords ?

Now from my point of view SQLSERVER connectionstring = MYSQL connection string.

Posted 12-Feb-15 9:03am

Member 10377426

Add a Solution

Comments

PIEBALDconsult 12-Feb-15 15:09pm

I wouldn't call it ambiguous. But I agree with trying to use common names as much as possible.

[no name] 12-Feb-15 15:16pm

but sir tell me the default connection string is good ?
i currently use that for MYSQL :
server = ip; database = dbname; uid= username; pwd=password;

so what you guess. using data source or server ?

PIEBALDconsult 12-Feb-15 15:20pm

I use Server and Database because it's common with other providers I use, e.g. MySQL .

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

**Zoltán Zörgő** · Answer 1 · 2015-02-12T09:13:00

If you consult this extensive list of connection string syntax: http://www.connectionstrings.com/[^], you will notice, that most providers have more than one connection string syntax. And yes, you might find overlapping - altrough you are wrong:
SQL Server standard syntax is:

Server=myServerAddress;Database=myDataBase;User Id=myUsername;<br />
Password=myPassword;

MySQL Standard syntax is what you have posted:
Server=myServerAddress;Database=myDataBase;Uid=myUsername;Pwd=myPassword;
So these are not equal, just similar. But what if? Nothing. Not the connection string defines the provider. It is just a string defining parameters. It is up to the provider manufacturer's choice to define this syntax. Could those be harmonized? Yes, maybe. But who would do this?