| Groups | Blog | Home |
dotnet windows forms : ConnectionString Without DSN
This is, by all accounts, a stupid question:
I've always used a connection string like this: Data Source=DSNNAME;Initial Catalog=databasename;Persist Security Info=True;User ID=sa;Password=pwd I don't want to have to go to every computer and create this DSN manually. How should the connection string read if you want to connect directly to the sql server without specifying or creating a DSN? Ross
Hi Ross,
See http://www.connectionstrings.com/ -- HTH, Kevin Spencer Chicken Salad Surgeon Microsoft MVP [quoted text, click to view] "Ross Culver" <rculver@warrenalloy.com> wrote in message news:e51mkjhJIHA.5980@TK2MSFTNGP04.phx.gbl... > This is, by all accounts, a stupid question: > > I've always used a connection string like this: > Data Source=DSNNAME;Initial Catalog=databasename;Persist Security > Info=True;User ID=sa;Password=pwd > > I don't want to have to go to every computer and create this DSN manually. > How should the connection string read if you want to connect directly to > the sql server without specifying or creating a DSN? > > Ross >
Stephany and Kevin,
Thanks for the response; however, I already tried using just the server name and I get the error that the datasource was not found. That's why I keep creating a DSN with the same name as the server. Ross [quoted text, click to view] "Stephany Young" <noone@localhost> wrote in message news:OLGyiclJIHA.4948@TK2MSFTNGP02.phx.gbl... > Data Source=<servername>;... > > or > > Data Source=<servername>\<instancename>;... > > > > "Ross Culver" <rculver@warrenalloy.com> wrote in message > news:e51mkjhJIHA.5980@TK2MSFTNGP04.phx.gbl... >> This is, by all accounts, a stupid question: >> >> I've always used a connection string like this: >> Data Source=DSNNAME;Initial Catalog=databasename;Persist Security >> Info=True;User ID=sa;Password=pwd >> >> I don't want to have to go to every computer and create this DSN >> manually. How should the connection string read if you want to connect >> directly to the sql server without specifying or creating a DSN? >> >> Ross >> >
Data Source=<servername>;...
or Data Source=<servername>\<instancename>;... [quoted text, click to view] "Ross Culver" <rculver@warrenalloy.com> wrote in message
news:e51mkjhJIHA.5980@TK2MSFTNGP04.phx.gbl... > This is, by all accounts, a stupid question: > > I've always used a connection string like this: > Data Source=DSNNAME;Initial Catalog=databasename;Persist Security > Info=True;User ID=sa;Password=pwd > > I don't want to have to go to every computer and create this DSN manually. > How should the connection string read if you want to connect directly to > the sql server without specifying or creating a DSN? > > Ross >
That's why I directed you to www.connectionstrings.com. Connection strings
vary from one database provider to another, and according to the type of connection being made, and guessing at the proper format will get you nowhere. As I don't know anything about either what database you're using, or what the connection properties should be, I directed you to a web site that provides all sorts of Connection Strings for all sorts of situations. Using a System DSN is really an "ancient" technique which creates an additional external dependency on the DSN. Look up the proper Connection String for your needs and use that. -- HTH, Kevin Spencer Chicken Salad Surgeon Microsoft MVP [quoted text, click to view] "Ross Culver" <rculver@warrenalloy.com> wrote in message news:ecd4lPtJIHA.5400@TK2MSFTNGP04.phx.gbl... > Stephany and Kevin, > > Thanks for the response; however, I already tried using just the server > name and I get the error that the datasource was not found. That's why I > keep creating a DSN with the same name as the server. > > Ross > > > "Stephany Young" <noone@localhost> wrote in message > news:OLGyiclJIHA.4948@TK2MSFTNGP02.phx.gbl... >> Data Source=<servername>;... >> >> or >> >> Data Source=<servername>\<instancename>;... >> >> >> >> "Ross Culver" <rculver@warrenalloy.com> wrote in message >> news:e51mkjhJIHA.5980@TK2MSFTNGP04.phx.gbl... >>> This is, by all accounts, a stupid question: >>> >>> I've always used a connection string like this: >>> Data Source=DSNNAME;Initial Catalog=databasename;Persist Security >>> Info=True;User ID=sa;Password=pwd >>> >>> I don't want to have to go to every computer and create this DSN >>> manually. How should the connection string read if you want to connect >>> directly to the sql server without specifying or creating a DSN? >>> >>> Ross >>> >> > >
Kevin,
I left out one very important piece of information: I created the connection in VS2K5 using the connection wizard using the .net framework data provider for SQL2K5 (SQL Client); wherein you select the server by name and never have to specify a DSN. And yet, it only works if I create a DSN with the same name as the server. Go figure. Ross [quoted text, click to view] "Kevin Spencer" <unclechutney@nothinks.com> wrote in message news:OpI$aS4JIHA.748@TK2MSFTNGP04.phx.gbl... > That's why I directed you to www.connectionstrings.com. Connection strings > vary from one database provider to another, and according to the type of > connection being made, and guessing at the proper format will get you > nowhere. As I don't know anything about either what database you're using, > or what the connection properties should be, I directed you to a web site > that provides all sorts of Connection Strings for all sorts of situations. > > Using a System DSN is really an "ancient" technique which creates an > additional external dependency on the DSN. Look up the proper Connection > String for your needs and use that. > > -- > HTH, > > Kevin Spencer > Chicken Salad Surgeon > Microsoft MVP > > "Ross Culver" <rculver@warrenalloy.com> wrote in message > news:ecd4lPtJIHA.5400@TK2MSFTNGP04.phx.gbl... >> Stephany and Kevin, >> >> Thanks for the response; however, I already tried using just the server >> name and I get the error that the datasource was not found. That's why I >> keep creating a DSN with the same name as the server. >> >> Ross >> >> >> "Stephany Young" <noone@localhost> wrote in message >> news:OLGyiclJIHA.4948@TK2MSFTNGP02.phx.gbl... >>> Data Source=<servername>;... >>> >>> or >>> >>> Data Source=<servername>\<instancename>;... >>> >>> >>> >>> "Ross Culver" <rculver@warrenalloy.com> wrote in message >>> news:e51mkjhJIHA.5980@TK2MSFTNGP04.phx.gbl... >>>> This is, by all accounts, a stupid question: >>>> >>>> I've always used a connection string like this: >>>> Data Source=DSNNAME;Initial Catalog=databasename;Persist Security >>>> Info=True;User ID=sa;Password=pwd >>>> >>>> I don't want to have to go to every computer and create this DSN >>>> manually. How should the connection string read if you want to connect >>>> directly to the sql server without specifying or creating a DSN? >>>> >>>> Ross >>>> >>> >> >> > >
Maybe you will have to break down and show us what you have tried that
doesn't work. On Thu, 15 Nov 2007 15:26:20 -0600, "Ross Culver" [quoted text, click to view] <rculver@warrenalloy.com> wrote:
>Kevin, > >I left out one very important piece of information: I created the >connection in VS2K5 using the connection wizard using the .net framework >data provider for SQL2K5 (SQL Client); wherein you select the server by >name and never have to specify a DSN. And yet, it only works if I create a >DSN with the same name as the server. > >Go figure. > >Ross > > >"Kevin Spencer" <unclechutney@nothinks.com> wrote in message >news:OpI$aS4JIHA.748@TK2MSFTNGP04.phx.gbl... >> That's why I directed you to www.connectionstrings.com. Connection strings >> vary from one database provider to another, and according to the type of >> connection being made, and guessing at the proper format will get you >> nowhere. As I don't know anything about either what database you're using, >> or what the connection properties should be, I directed you to a web site >> that provides all sorts of Connection Strings for all sorts of situations. >> >> Using a System DSN is really an "ancient" technique which creates an >> additional external dependency on the DSN. Look up the proper Connection >> String for your needs and use that. >> >> -- >> HTH, >> >> Kevin Spencer >> Chicken Salad Surgeon >> Microsoft MVP >> >> "Ross Culver" <rculver@warrenalloy.com> wrote in message >> news:ecd4lPtJIHA.5400@TK2MSFTNGP04.phx.gbl... >>> Stephany and Kevin, >>> >>> Thanks for the response; however, I already tried using just the server >>> name and I get the error that the datasource was not found. That's why I >>> keep creating a DSN with the same name as the server. >>> >>> Ross >>> >>> >>> "Stephany Young" <noone@localhost> wrote in message >>> news:OLGyiclJIHA.4948@TK2MSFTNGP02.phx.gbl... >>>> Data Source=<servername>;... >>>> >>>> or >>>> >>>> Data Source=<servername>\<instancename>;... >>>> >>>> >>>> >>>> "Ross Culver" <rculver@warrenalloy.com> wrote in message >>>> news:e51mkjhJIHA.5980@TK2MSFTNGP04.phx.gbl... >>>>> This is, by all accounts, a stupid question: >>>>> >>>>> I've always used a connection string like this: >>>>> Data Source=DSNNAME;Initial Catalog=databasename;Persist Security >>>>> Info=True;User ID=sa;Password=pwd >>>>> >>>>> I don't want to have to go to every computer and create this DSN >>>>> manually. How should the connection string read if you want to connect >>>>> directly to the sql server without specifying or creating a DSN? >>>>> >>>>> Ross >>>>> >>>> >>> >>> >> >>
The Visual Studio 2005 Connection Wizard doesn't ask for a DSN. I don't know
what you're referring to. It asks for any number of Connection String parameters. You can also just create your own Connection String. -- HTH, Kevin Spencer Chicken Salad Surgeon Microsoft MVP [quoted text, click to view] "Ross Culver" <rculver@warrenalloy.com> wrote in message news:OyZJW38JIHA.2064@TK2MSFTNGP06.phx.gbl... > Kevin, > > I left out one very important piece of information: I created the > connection in VS2K5 using the connection wizard using the .net framework > data provider for SQL2K5 (SQL Client); wherein you select the server by > name and never have to specify a DSN. And yet, it only works if I create > a DSN with the same name as the server. > > Go figure. > > Ross > > > "Kevin Spencer" <unclechutney@nothinks.com> wrote in message > news:OpI$aS4JIHA.748@TK2MSFTNGP04.phx.gbl... >> That's why I directed you to www.connectionstrings.com. Connection >> strings vary from one database provider to another, and according to the >> type of connection being made, and guessing at the proper format will get >> you nowhere. As I don't know anything about either what database you're >> using, or what the connection properties should be, I directed you to a >> web site that provides all sorts of Connection Strings for all sorts of >> situations. >> >> Using a System DSN is really an "ancient" technique which creates an >> additional external dependency on the DSN. Look up the proper Connection >> String for your needs and use that. >> >> -- >> HTH, >> >> Kevin Spencer >> Chicken Salad Surgeon >> Microsoft MVP >> >> "Ross Culver" <rculver@warrenalloy.com> wrote in message >> news:ecd4lPtJIHA.5400@TK2MSFTNGP04.phx.gbl... >>> Stephany and Kevin, >>> >>> Thanks for the response; however, I already tried using just the server >>> name and I get the error that the datasource was not found. That's why >>> I keep creating a DSN with the same name as the server. >>> >>> Ross >>> >>> >>> "Stephany Young" <noone@localhost> wrote in message >>> news:OLGyiclJIHA.4948@TK2MSFTNGP02.phx.gbl... >>>> Data Source=<servername>;... >>>> >>>> or >>>> >>>> Data Source=<servername>\<instancename>;... >>>> >>>> >>>> >>>> "Ross Culver" <rculver@warrenalloy.com> wrote in message >>>> news:e51mkjhJIHA.5980@TK2MSFTNGP04.phx.gbl... >>>>> This is, by all accounts, a stupid question: >>>>> >>>>> I've always used a connection string like this: >>>>> Data Source=DSNNAME;Initial Catalog=databasename;Persist Security >>>>> Info=True;User ID=sa;Password=pwd >>>>> >>>>> I don't want to have to go to every computer and create this DSN >>>>> manually. How should the connection string read if you want to connect >>>>> directly to the sql server without specifying or creating a DSN? >>>>> >>>>> Ross >>>>> >>>> >>> >>> >> >> > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |