I would like to be able to connect to a remote SQL Server and fire arbitrary
queries, browse tables, and so forth.  Very much like MS's "SQL Server Web
Data Administrator" (link:
http://www.microsoft.com/downloads/details ...

I wrote a conversion program to convert some dbf data to an sql server 2000.
When I run the program on a Windows 2000 SP4 everything works fine. When
I run the same program on a Windows XP SP2 the program is really slow.
Haven't tried the program on a xp without sp 2. Maybe SP is ...

I am in the process of trying to evaluate setting up a System Area
Network and linking several SQL servers using the VIA protocol. I am
having some difficulties in finding good resources on how to go about
setting one up. I'm also having difficulty finding a good variety of

Greetings -
I'm working with a SQL Server 2000 database via an Access front-end and I'd
like to check if the user has a login (via a pass through query I imagine) on
the database before attempting to pass the connection  string.  The user

I can address Linked Oracle Tables with no catalog name but I CANNOT address
MySQL tables with no Schema Name
MySQL_LinkName.CatalogName.SchemaName.TableName
For Oracle I use with no problem:

i habe some trouble with a sql 2000 appclication
The envisonment:
SQL-2000 - Server MS Access2000 - Client that uses SQL server tables via
ODBC.

I have a great problem with Sql Server connections in Pocket Pc. When I try
to create a connection with an Sql Server 2000 with Visual Basic.NET 2003 (I
have Windows XP), I receive the error : "SQL Server does not exist or access
denied".

We have been using Microsoft SQL Server JDBC Driver 2.2.0040 in our products
to connect to SQL Server 2000 Standard Edition SP3 (8.00.760).  Our
functional testing went fine but we have run into serious performance
degradation under simulated heavy loads.

I'm trying to create a ODBC connection to SQL server 2000 using SQL server authentication. I have login id "lucky9797" and password "tool" but I'm keep getting the following error message:
      Connection Failed:
      SQLState:'28000'
      SQL Server Error: 18456

I am asking a generic question about SQL server (or any type server
communication for that matter) and how one would keep the connection open
for the life time of the application, or should one close the connection for
each request (or set of related requests)?

Have just changed over from Access to SQL server 2000.
Having connection difficulty at one client only!! 2 pcs on network - both
win 98.
Local machine connects to server fine, but when connecting to sql server via

I have SQL server 7 running as a default instance and I'm trying to install
MSDE 2000.  I was able to install it as a named instance by running the
following:
setup.exe SAPWD="password" INSTANCENAME="named_instance"

Is this doable?
The server name is TOPAZ
The alias name is topaz-alias
The username is somesqldb

We are currently running SQL Server 7.0 with databases in 6.5-compatibility
mode for DB-Library.
- Will this still be supported in Sql Server 2005?
- If so, any changes in behaviour?

how to unistall MDAC 2.8?