Guys,
Anybody knows how the client network utility can be configured PROGRAMATICALLY.
What I wanna do ultimately, is to run a batch file and set an alias for the client network utility.
Thanks,
Regards,Any possibilities thru OSQL? I haven't found anything yet.|||Double posting. :)|||I'm pretty sure that you can do it with a registry file... don't have SQL Server on my new laptop yet so I can't tell you what key, but it should be in HKEY_LOCAL_MACHINE somewhere
all you should have to do is set it up, do a search in the registry (using regedit) for the alias or whatever you added, export that key to a *.reg file, clean up the file a bit (to get rid of duplicate or extraneous keys) and import it on a test machine to check it out.
I use that method to add system ODBC data sources all the time, never done it with the Client Network Utility though... standard disclaimer however... if you mess up the registry it's your fault and don't forget to back it up before importing anything|||Hey thanx Drew. Interesting idea. I'll give it a try and let you know what happened.|||sure thing... I'll be in the office tomorrow and will post it up if I get to it before you, been meaning to do it for a long time to make client config as dummy proof as possible so I don't have to sit on the phone t-shooting stupid crap like that
Showing posts with label configured. Show all posts
Showing posts with label configured. Show all posts
Thursday, February 16, 2012
Client Network Utility
Sunday, February 12, 2012
Client Application and SQL Mirroring
I have an application where the SQL Database is configured within (I give it
the server name, database name and SQL access info). I did not write the app
and was wondering if it could be used with SQL mirroring high availability
without having to reconfigure the client app.
I skimmed over the link 'SQL Server 2005 Books Online Overview of Database
Mirroring' http://msdn2.microsoft.com/en-us/library/ms189852.aspx and still
am not clear about how the client application sees the mirrored database on a
failure when using the top level mirroring feature - High Availability.
Thanks
New2SQLHi
From www.connectionstrings.com
/*
If you connect with ADO.NET or the SQL Native Client to a database that is
being mirrored, your application can take advantage of the drivers ability
to automatically redirect connections when a database mirroring failover
occurs. You must specify the initial principal server and database in the
connection string and the failover partner server.
Data Source=myServerAddress;Failover Partner=myMirrorServer;Initial
Catalog=myDataBase;Integrated Security=True;
*/
"New2SQL" <New2SQL@.discussions.microsoft.com> wrote in message
news:189496E6-29DC-484B-961F-F8E895363558@.microsoft.com...
>I have an application where the SQL Database is configured within (I give
>it
> the server name, database name and SQL access info). I did not write the
> app
> and was wondering if it could be used with SQL mirroring high availability
> without having to reconfigure the client app.
> I skimmed over the link 'SQL Server 2005 Books Online Overview of Database
> Mirroring' http://msdn2.microsoft.com/en-us/library/ms189852.aspx and
> still
> am not clear about how the client application sees the mirrored database
> on a
> failure when using the top level mirroring feature - High Availability.
> Thanks
> New2SQL
>
the server name, database name and SQL access info). I did not write the app
and was wondering if it could be used with SQL mirroring high availability
without having to reconfigure the client app.
I skimmed over the link 'SQL Server 2005 Books Online Overview of Database
Mirroring' http://msdn2.microsoft.com/en-us/library/ms189852.aspx and still
am not clear about how the client application sees the mirrored database on a
failure when using the top level mirroring feature - High Availability.
Thanks
New2SQLHi
From www.connectionstrings.com
/*
If you connect with ADO.NET or the SQL Native Client to a database that is
being mirrored, your application can take advantage of the drivers ability
to automatically redirect connections when a database mirroring failover
occurs. You must specify the initial principal server and database in the
connection string and the failover partner server.
Data Source=myServerAddress;Failover Partner=myMirrorServer;Initial
Catalog=myDataBase;Integrated Security=True;
*/
"New2SQL" <New2SQL@.discussions.microsoft.com> wrote in message
news:189496E6-29DC-484B-961F-F8E895363558@.microsoft.com...
>I have an application where the SQL Database is configured within (I give
>it
> the server name, database name and SQL access info). I did not write the
> app
> and was wondering if it could be used with SQL mirroring high availability
> without having to reconfigure the client app.
> I skimmed over the link 'SQL Server 2005 Books Online Overview of Database
> Mirroring' http://msdn2.microsoft.com/en-us/library/ms189852.aspx and
> still
> am not clear about how the client application sees the mirrored database
> on a
> failure when using the top level mirroring feature - High Availability.
> Thanks
> New2SQL
>
Subscribe to:
Posts (Atom)