Re: Problems connecting to SQL Server

inline

--
Keith Kratochvil


"Cary Shultz" <cwshultz@xxxxxxxx> wrote in message
news:ed5t6rLYGHA.3740@xxxxxxxxxxxxxxxxxxxxxxx
Good afternoon!

I am a complete newbie when it comes to SQL, so please be gentle!

We have a mission-critical application that runs on a WINNT 4 SP6a/SQL 7
SP4 PDC (This was setup several years ago - way before my time). There
are three clients that use this application - but they use it a ton!!!!
One of the clients suffered from a hard drive crash.

Anyway, I replaced the hard drive and loaded WIN2000 Pro SP4 with all
patches. I am trying to install the ODBC driver but do not know the SA
password (a whole other issue). Not sure that we know the SYSADM password
either (not sure if this is a SQL account or a Maximo account - I think
that later). So, I can not connect from this machine to the SQL Server.

You should not need to know the sa password to install the ODBC driver. You
can install the latest (or appropriate) MDAC.
I don't know what method you use to connect to the database server. There
are two methods: SQL Server Authentication and Windows NT (integrated)
authentication. With SQL Server Authentication you need to specify a
user/pwd combination that is validated by SQL Server. With NT
authentication your database server relies on the security built into
Windows in order to validate users. You would then allow users [windows
logins]or [network] groups to connect to your database server and have the
appropriate level of access.


I have seen in the documentation for Maximo that I need to install the SQL
Client software. I assume that this is on the SQL Server CD (another
problem is that I have the SQL 7.0 Installation Media but do not have the
Product Key....it just keeps getting better!). I do not see that the SQL
Client software was installed on the other two stations (one WIN2000 and
one WINXP). Is this necessary (I told you that I am a complete newbie!)?
Does installing the SQL Client software help in establishing a connection
from client to server?

It is rare that you need to install the SQL Server client on a client
machine in order for an application to work. If the goal is to get the ODBC
components updated, simply make sure that you install whatever version of
MDAC that you need.


Also, I want to make sure that in my attempts to resolve this connection
issue that I do not break the connection for the other two. That would be
really bad!

You should be ok as long as you do not change any security related
configuration within the database server.


Maximo (read: MRO Software) has been very helpful but, rightly so, states
that this part of the problem is a SQL issue and not a Maximo issue.

Right. But, do they recommend connecting to the database using SQL Server
Authentication or Windows Authentication? I suppose that you can LOOK (but
don't modify) the user, file, and system DSNs on your other client boxes.


Can anyone offer any advice? I would be most grateful. I find myself in
a rather difficult situation and the affected user is starting to loose
his patience. As are the other two (because he needs to sit on their
computers to use Maximo).

--
Cary W. Shultz
Roanoke, VA 24012



.

Relevant Pages

  • Re: SBS 2003 and Sql Server ~ Client Install
    ... I've found the client tools and have now ... A word mail merge document could access a SQL database via ... We want to install to gain an understanding. ... Once we've managed to install the SQL Server Client we can start to ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: SQL Server 2005 Cluster Setup Quiz
    ... I did test and it did not install the client tools. ... http://www.clusterhelp.com - Cluster Training ... Microsoft SQL Server MVP ... Provide a template on how to read SQL Server 2005 setup log files. ...
    (microsoft.public.sqlserver.clustering)
  • Re: WSS 3.0 question
    ... I followed the advise given in removing WSS 3.0 etc, ... the server is complaining that the SQL service(?) was tempered with or corrupt. ... I may just instal the SQL server as I was going eventuall use it anyway. ... If WSUS 3.0 is installed, I would suggest you uninstall it and then you install WSS 3.0. ...
    (microsoft.public.windows.server.sbs)
  • Re: Trying to Move Group - SQL Instance Wont Start
    ... You can do a maintenance install and add the new nodes. ... "maintaining a failover cluster" for recovery from failure scenario 1. ... Senior SQL Infrastructure Consultant ... Microsoft SQL Server MVP ...
    (microsoft.public.sqlserver.clustering)
  • Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
    ... While attempting to install SP4, it comes up immediately after I ... to be on one of the nodes that can bring SQL Server online and apply SP3a, ...
    (microsoft.public.sqlserver.clustering)