Connect to Remote SQL
From: Des Norton (des_at_gencentric.co.za)
Date: 03/25/04
- Next message: Tibor Karaszi: "Re: Query Analyser - how do i terminate a script"
- Previous message: Jacco Schalkwijk: "Re: Query Analyser - how do i terminate a script"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 25 Mar 2004 12:02:52 +0200
Hi NG
I am not sure if this is the correct group for my question.
Background:
* I am distributing an application which is reliant on MSSQL 7+ .
* If the client does not already have MSSQL running on their network, I
will install an instance of MSDE.
Assume:
* Client machine (where my app is being installed) is *CLEAN* - Only
OS - Win 95+
* Client machine is a member of a domain
* MSSQL already available on the domain
* MSSQL uses SQL Authentication
I can use Win32APIs to discover all the MSSQL servers running in the domain.
My problems are as follows:
1. (Nice to have) I am unable to determine Instance Names
2. User selects Server, and supplies the sa password - I build the
ConnectionString, but need to be able to test before continuing.
* I believe that OSQL will allow me to determine the instance names, and
test for a connection. It will even allow me to run various scripts, but
this will be taken care of by my setup package at the end of the
installation.
* Assuming that I package OSSQL with my app for the express purpose of 1
and 2 above, and that it will be deleted as soon as the above is completed.
Can somebody help me with a list of dependancy files for OSQL.exe (DLLs,
OCXs, etc) that I will need in order to be able to use OSQL on the client.
Thank you
Des Norton
- Next message: Tibor Karaszi: "Re: Query Analyser - how do i terminate a script"
- Previous message: Jacco Schalkwijk: "Re: Query Analyser - how do i terminate a script"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
