Allowing a client to connect to SQL Server

Allowing a client to connect to SQL Server

Post by Brian Ra » Sat, 12 May 2001 07:07:53



Is it possible for another user on another machine to remotely connect to
SQL server to adminster thier database?

E.g. I've created an SQL Database, setup a user/pass for that database...
now a user from a remote machine is trying to use that user/pass to remotely
connect to the SQL Server to administer things like creating tables,etc.
through the SQL Interface.

- Brian

 
 
 

Allowing a client to connect to SQL Server

Post by Brian Mora » Sat, 12 May 2001 11:32:02


yes.

are you having a problem connecting, or were you just asking?

--
Brian Moran


Quote:> Is it possible for another user on another machine to remotely connect to
> SQL server to adminster thier database?

> E.g. I've created an SQL Database, setup a user/pass for that database...
> now a user from a remote machine is trying to use that user/pass to
remotely
> connect to the SQL Server to administer things like creating tables,etc.
> through the SQL Interface.

> - Brian


 
 
 

Allowing a client to connect to SQL Server

Post by Dan Guzma » Sat, 12 May 2001 11:35:01


Yes, it is common to connect to SQL Server remotely using Enterprise Manager
or Query Analyzer to perform these tasks.  Depending on your SQL Server
security configuration, you can use either SQL Server authentication (userid
and password) or Windows authentication.

Hope this helps.

-----------------------
SQL FAQ links (courtesy  Neil Pike):

 http://forumsb.compuserve.com/gvforums/UK/default.asp?SRV=MSDevApps
 (faqxxx.zip in lib 7)
 or www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
 or www.sqlserverfaq.com
 or www.mssqlserver.com/faq
-----------------------


Quote:> Is it possible for another user on another machine to remotely connect to
> SQL server to adminster thier database?

> E.g. I've created an SQL Database, setup a user/pass for that database...
> now a user from a remote machine is trying to use that user/pass to
remotely
> connect to the SQL Server to administer things like creating tables,etc.
> through the SQL Interface.

> - Brian

 
 
 

Allowing a client to connect to SQL Server

Post by Brian Ra » Sat, 12 May 2001 12:24:45


Well, I was having a problem.

The user keeps getting "Access Denied" even though the u/p is correct and
the sql server ip is correct.

One thing though,the user isnt running the latest service packs. Would the
user need to upgrade to the latest version?


> Yes, it is common to connect to SQL Server remotely using Enterprise
Manager
> or Query Analyzer to perform these tasks.  Depending on your SQL Server
> security configuration, you can use either SQL Server authentication
(userid
> and password) or Windows authentication.

> Hope this helps.

> -----------------------
> SQL FAQ links (courtesy  Neil Pike):

>  http://forumsb.compuserve.com/gvforums/UK/default.asp?SRV=MSDevApps
>  (faqxxx.zip in lib 7)
>  or www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
>  or www.sqlserverfaq.com
>  or www.mssqlserver.com/faq
> -----------------------



> > Is it possible for another user on another machine to remotely connect
to
> > SQL server to adminster thier database?

> > E.g. I've created an SQL Database, setup a user/pass for that
database...
> > now a user from a remote machine is trying to use that user/pass to
> remotely
> > connect to the SQL Server to administer things like creating tables,etc.
> > through the SQL Interface.

> > - Brian

 
 
 

Allowing a client to connect to SQL Server

Post by Dan Guzma » Sat, 12 May 2001 12:50:39


I won't discourage installing the latest SP, although that probably isn't
the problem here.

You might try running the Client Network utility on the PC to specify TCP/IP
as the protocol.

Hope this helps.


> Well, I was having a problem.

> The user keeps getting "Access Denied" even though the u/p is correct and
> the sql server ip is correct.

> One thing though,the user isnt running the latest service packs. Would the
> user need to upgrade to the latest version?



> > Yes, it is common to connect to SQL Server remotely using Enterprise
> Manager
> > or Query Analyzer to perform these tasks.  Depending on your SQL Server
> > security configuration, you can use either SQL Server authentication
> (userid
> > and password) or Windows authentication.

> > Hope this helps.

> > -----------------------
> > SQL FAQ links (courtesy  Neil Pike):

> >  http://forumsb.compuserve.com/gvforums/UK/default.asp?SRV=MSDevApps
> >  (faqxxx.zip in lib 7)
> >  or www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
> >  or www.sqlserverfaq.com
> >  or www.mssqlserver.com/faq
> > -----------------------



> > > Is it possible for another user on another machine to remotely connect
> to
> > > SQL server to adminster thier database?

> > > E.g. I've created an SQL Database, setup a user/pass for that
> database...
> > > now a user from a remote machine is trying to use that user/pass to
> > remotely
> > > connect to the SQL Server to administer things like creating
tables,etc.
> > > through the SQL Interface.

> > > - Brian

 
 
 

1. I can not connect SQL server 7.0 using SQL server 7.0 client

Dear all,
    I have a stupid question,I do not know how the DBA installed the SQL
server 7.0,I can not connect SQL server 7.0 using SQL server 7.0 client, the
SQL server 7.0 name is "AAA\BB",I try to use the server-side sql manager to
connect to the database ,when i choose 'Local',it also failed ,but when I
input "AAA\BB",it can connect successfully,why,any helpful idea will be
appreciated ,thanks
                                alex

2. Lotus Approach

3. SQL Server client can not connect to SQL Server

4. Identification Number

5. Can connect to SQL 2000 server from 7.0 client, not from 2000 client

6. Update row during insert trigger

7. Allowed to connect to SQL Server using Bridge?

8. null records

9. Allowing only certain clients access to SQL Server 2K

10. Newbie - connect SQL Server 2000 client to Internet Server

11. Connecting a SQL SERVER 2000 Database in NT Server From NT/98 Client

12. Problem connecting to different versions of SQL server from SQL 2000 client

13. HP network not allowing client server to work