Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Starting SQL Server remotely

8 posts in Windows NT Last posting was on 1997-10-31 10:10:37.0Z
Patrick R. Sklenar Posted on 1997-06-25 14:21:04.0Z
Message-ID: <33B12950.C5D44BC3@uhcip6a5.uhc.com>
Date: Wed, 25 Jun 1997 10:21:04 -0400
From: "Patrick R. Sklenar" <psklena@uhcip6a5.uhc.com>
Organization: United HealthCare Corp. - IT/DP&S
X-Mailer: Mozilla 4.01 [en] (WinNT; I)
MIME-Version: 1.0
Subject: Starting SQL Server remotely
X-Priority: 3 (Normal)
Content-Type: multipart/mixed; boundary="------------44F1DA3AB94599AD1E8D74E9"
Newsgroups: sybase.public.sqlserver.nt
Lines: 48
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.sqlserver.nt:5604
Article PK: 1081678

SQL Server System 11.0.x for NT is different than Unix in more ways
that I originally expected. How can I remotely start a SQL Server? In
other words, I'm located in Hartford, CT and I have a Syabse SQL Server
located in Minneapolis, MN. It's not like I can walk over to another
building or something. How can I start that SQL Server?

Sybase Central (aka: SQL Central) will let me SHUTDOWN a server, but
not start it (well, actually it will start a *LOCAL* server, but not one
on another box). Help!! I've got to figure out how to do this.

I can start Unix Sybase SQL Servers remotely via the startserver
executable and a RUN_Server file. I can start Microsoft NT SQL Servers
remotely via SQL Service Manager *AND* via SQL Enterprise Managers
(MS's, more mature, answer to Sybase Central). But, I can't figure out
how to start Sybase SQL Server for NT remotely. Help!!!

pat----


Download VCard vcard.vcf


David Pascuzzi Posted on 1997-10-21 16:17:07.0Z
Message-ID: <344CD583.E270D035@neonsoft.com>
Date: Tue, 21 Oct 1997 10:17:07 -0600
From: David Pascuzzi <dpascuzzi@neonsoft.com>
X-Mailer: Mozilla 4.03 [en] (WinNT; I)
MIME-Version: 1.0
To: "Patrick R. Sklenar" <psklena@uhcip6a5.uhc.com>
Subject: Re: Starting SQL Server remotely
References: <33B12950.C5D44BC3@uhcip6a5.uhc.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.sqlserver.nt
Lines: 50
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.sqlserver.nt:5471
Article PK: 1081548

Patrick,

another option to starting SQL Server Remotely is to buy a telnet package for you server.
Telnet onto the server and then start the sql server using the .bat file

Patrick R. Sklenar wrote:

> SQL Server System 11.0.x for NT is different than Unix in more ways
> that I originally expected. How can I remotely start a SQL Server? In
> other words, I'm located in Hartford, CT and I have a Syabse SQL Server
> located in Minneapolis, MN. It's not like I can walk over to another
> building or something. How can I start that SQL Server?
>
> Sybase Central (aka: SQL Central) will let me SHUTDOWN a server, but
> not start it (well, actually it will start a *LOCAL* server, but not one
> on another box). Help!! I've got to figure out how to do this.
>
> I can start Unix Sybase SQL Servers remotely via the startserver
> executable and a RUN_Server file. I can start Microsoft NT SQL Servers
> remotely via SQL Service Manager *AND* via SQL Enterprise Managers
> (MS's, more mature, answer to Sybase Central). But, I can't figure out
> how to start Sybase SQL Server for NT remotely. Help!!!
>
> pat----
>
> ------------------------------------------------------------------------
>
> Sklenar, Patrick (at work) <psklena@uhcip6a5.uhc.com>
> Dist. DB Product Support Analyst
> United HealthCare Corp. - DP&S
>
> Sklenar, Patrick (at work)
> Dist. DB Product Support Analyst <psklena@uhcip6a5.uhc.com>
> United HealthCare Corp. - DP&S
> 450 Columbus Blvd. - 6GB Work: (860) 702-5845
> UHC Mail Route: CT029 06BB Fax: (860) 702-5944
> Hartford Netscape Conference Address
> CT Netscape Conference DLS Server
> 06040-0450
> USA
> Sybase & MS DBMS in-house product support
> Additional Information:
> Last Name Sklenar
> First NamePatrick (at work)


Reinoud van Leeuwen Posted on 1997-10-31 10:10:37.0Z
Message-ID: <3459AE9D.6935@sybase.com>
Date: Fri, 31 Oct 1997 11:10:37 +0100
From: Reinoud van Leeuwen <reinoud@sybase.com>
Organization: Sybase Inc.
X-Mailer: Mozilla 3.0 (Win95; I)
MIME-Version: 1.0
Subject: Re: Starting SQL Server remotely
References: <33B12950.C5D44BC3@uhcip6a5.uhc.com> <344CD583.E270D035@neonsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.sqlserver.nt
Lines: 49
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.sqlserver.nt:5441
Article PK: 1081519


David Pascuzzi wrote:
>
> Patrick,
>
> another option to starting SQL Server Remotely is to buy a telnet package for you server.
> Telnet onto the server and then start the sql server using the .bat file
>
> Patrick R. Sklenar wrote:
>
> > SQL Server System 11.0.x for NT is different than Unix in more ways
> > that I originally expected. How can I remotely start a SQL Server? In
> > other words, I'm located in Hartford, CT and I have a Syabse SQL Server
> > located in Minneapolis, MN. It's not like I can walk over to another
> > building or something. How can I start that SQL Server?
> >
> > Sybase Central (aka: SQL Central) will let me SHUTDOWN a server, but
> > not start it (well, actually it will start a *LOCAL* server, but not one
> > on another box). Help!! I've got to figure out how to do this.
> >
> > I can start Unix Sybase SQL Servers remotely via the startserver
> > executable and a RUN_Server file. I can start Microsoft NT SQL Servers
> > remotely via SQL Service Manager *AND* via SQL Enterprise Managers
> > (MS's, more mature, answer to Sybase Central). But, I can't figure out
> > how to start Sybase SQL Server for NT remotely. Help!!!
> >

The possiblity to remotely start a Sybase SQL server under NT is
somewhat hidden. It can be done with the NT server manager (which can be
installed on NT workstation too).

- Start svrmgr.exe with a command-line option of the server you want to
administer
(svrmgr \\NT_SERVER_WITH_SYBASE), or start it without options and
select a server with
the menu.
- klick ONCE on the server if you have a list
- select the "services" from the "computer" menu
- select the Sybase SQLServer_YOUR_SYBASE_SERVER_NAME
- klick on start

(this assumes that you're logged on the domain with sufficient
rights...)

Reinoud van Leeuwen
Sybase Professional Services Maarssen / The Netherlands


Dave Kaufman Posted on 1997-06-25 21:29:49.0Z
X-Newsreader: Microsoft Outlook Express 4.71.0544.0
From: "Dave Kaufman" <davidk@cnct.com>
References: <33B12950.C5D44BC3@uhcip6a5.uhc.com>
Subject: Re: Starting SQL Server remotely
Date: Wed, 25 Jun 1997 17:29:49 -0400
Lines: 30
X-MimeOLE: Produced By Microsoft MimeOLE Engine V4.71.0544.0
Message-ID: <jVDUeZag8GA.205@forums.powersoft.com>
Newsgroups: sybase.public.sqlserver.nt
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.sqlserver.nt:5603
Article PK: 1081681

The Windows NT Resource Kit contains a directory full of Remote NT
Administration tools which run on NTWS or W95 machines over LAN, WAN,
Internet, hill and dale.

Once your SQL server is installed as an NT "service", you can start it,
stop it, enable and disable it, set auto-startup-on-boot, etc. for ALL NT
services. You can also view error and security logs, administer users,
share drives, and restart the server. The only thing you *can't* do is
press the reset switch.

Patrick R. Sklenar wrote in article <33B12950.C5D44BC3@uhcip6a5.uhc.com>...

>SQL Server System 11.0.x for NT is different than Unix in more ways
>that I originally expected. How can I remotely start a SQL Server? In
>other words, I'm located in Hartford, CT and I have a Syabse SQL Server
>located in Minneapolis, MN. It's not like I can walk over to another
>building or something. How can I start that SQL Server?
>
> Sybase Central (aka: SQL Central) will let me SHUTDOWN a server, but
>not start it (well, actually it will start a *LOCAL* server, but not one
>on another box). Help!! I've got to figure out how to do this.
>
> I can start Unix Sybase SQL Servers remotely via the startserver
>executable and a RUN_Server file. I can start Microsoft NT SQL Servers
>remotely via SQL Service Manager *AND* via SQL Enterprise Managers
>(MS's, more mature, answer to Sybase Central). But, I can't figure out
>how to start Sybase SQL Server for NT remotely. Help!!!
>
> pat----


Patrick R. Sklenar Posted on 1997-06-26 12:48:54.0Z
Message-ID: <33B26536.FD8A07E0@uhcip6a5.uhc.com>
Date: Thu, 26 Jun 1997 08:48:54 -0400
From: "Patrick R. Sklenar" <psklena@uhcip6a5.uhc.com>
Organization: United HealthCare Corp. - IT/DP&S
X-Mailer: Mozilla 4.01 [en] (WinNT; I)
MIME-Version: 1.0
Subject: Re: Starting SQL Server remotely
X-Priority: 3 (Normal)
References: <33B12950.C5D44BC3@uhcip6a5.uhc.com> <jVDUeZag8GA.205@forums.powersoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.sqlserver.nt
Lines: 39
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.sqlserver.nt:5600
Article PK: 1081677


Dave Kaufman wrote:

> The Windows NT Resource Kit contains a directory full of Remote NT
> Administration tools which run on NTWS or W95 machines over LAN, WAN,
> Internet, hill and dale.
>
> Once your SQL server is installed as an NT "service", you can start
> it, stop it, enable and disable it, set auto-startup-on-boot, etc.
> for ALL NT services. You can also view error and security logs,
> administer users, share drives, and restart the server. The only
> thing you *can't* do is press the reset switch.

Dave,

Thanks for the reply. We've looked at the Resource Kit, but have a
serious problem with it. For us to be able to start NT services
remotely (i.e.: Sybase SQL Server), we have to be Administrative users
on the database server. This is a serious breach of my companies
corporate security implementation. We're not allowed 'root' access to
the UNIX database servers, and we're not going to be allowed
'administrator' access to the NT boxes.

Since I can start UNIX Sybase remotely under these rules, I have to be
able to do the same under NT Sybase. There *HAS* to be a way to do this
without requiring 'administrator' authority. If not, my area will have
to rethink our recommendation that the corporation use Sybase SQL
Server, instead of Microsoft SQL Server, on our NT boxes. :(

I really hope someone from Sybase/Powersoft is reading this newsgroup
and can set my mind at ease. I guess I'm going to have to call Sybase
TS and open a case on this as well. <sigh>

pat----


Dave Kaufman Posted on 1997-06-27 09:22:04.0Z
X-Newsreader: Microsoft Outlook Express 4.71.0544.0
From: "Dave Kaufman" <davidk@cnct.com>
References: <33B12950.C5D44BC3@uhcip6a5.uhc.com> <jVDUeZag8GA.205@forums.powersoft.com> <33B26536.FD8A07E0@uhcip6a5.uhc.com>
Subject: Re: Starting SQL Server remotely
Date: Fri, 27 Jun 1997 05:22:04 -0400
Lines: 72
X-MimeOLE: Produced By Microsoft MimeOLE Engine V4.71.0544.0
Message-ID: <nP5CAMtg8GA.162@forums.powersoft.com>
Newsgroups: sybase.public.sqlserver.nt
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.sqlserver.nt:5599
Article PK: 1081675


Patrick R. Sklenar wrote in article <33B26536.FD8A07E0@uhcip6a5.uhc.com>...

>Dave Kaufman wrote:
>
>> The Windows NT Resource Kit contains a directory full of Remote NT
>> Administration tools which run on NTWS or W95 machines over LAN, WAN,
[...]
>> Once your SQL server is installed as an NT "service", you can start
>> it, stop it, enable and disable it, set auto-startup-on-boot, etc.
[...]
>Dave,
>
> Thanks for the reply. We've looked at the Resource Kit, but have a

looking at it doesn't really do much; you have to read the manual...

>serious problem with it. For us to be able to start NT services
>remotely (i.e.: Sybase SQL Server), we have to be Administrative users
>on the database server. This is a serious breach of my companies
Not true. You have to be granted a single Administrative right. No big
deal.

>corporate security implementation. We're not allowed 'root' access to
>the UNIX database servers, and we're not going to be allowed
>'administrator' access to the NT boxes.
Oh well, then give up.

Look, if you just like UNIX, use UNIX. But if you want to give NT a
chance, give NT a chance. If you take even the merest look at an NT User
Database screen you'll find that there are dozens upon dozens of individual
rights that can be granted to a group of users without giving them "the"
Administrator equivalent access level. Most of these rights are designed
for giving developers and "sub-administrators" the right to do their work
without giving them access to other users' files, etc. For instance,
although every NT shop I've ever developed in had an administer who
assigned rights and had "root" level rights himself, development teams were
given the right to log onto the server locally, start and stop services,
administer print jobs, etc. on the development server. However on
production servers it was assumed that these things would be done by
properly trained dba's only.

> Since I can start UNIX Sybase remotely under these rules, I have to be
>able to do the same under NT Sybase. There *HAS* to be a way to do this
>without requiring 'administrator' authority. If not, my area will have
There is...
>to rethink our recommendation that the corporation use Sybase SQL
>Server, instead of Microsoft SQL Server, on our NT boxes. :(
...but maybe you should anyway.

Rethink whether you want NT or are being forced to use it. Rethink whether
your UNIX administrators should control the NT development servers if they
don't know how to configure the security database. By the way, MS SQL
Server has the same restrictions on starting and stopping services as SQL
Anywhere or any other product which runs as an NT service. See below...

> I really hope someone from Sybase/Powersoft is reading this newsgroup
>and can set my mind at ease. I guess I'm going to have to call Sybase
>TS and open a case on this as well. <sigh>
or you could politely ask your Administrators to do their jobs and set your
mind at ease. This is really a no-brainer...

People from Sybase read and post to these groups constantly (as you'll
likely notice if you read down about three or four more messages).

But it's not a Sybase/Powersoft thing; it's a Microsoft NT thing.

Good luck.

-Dave Kaufman


Dave Kaufman Posted on 1997-06-27 10:58:01.0Z
X-Newsreader: Microsoft Outlook Express 4.71.0544.0
From: "Dave Kaufman" <davidk@cnct.com>
References: <33B12950.C5D44BC3@uhcip6a5.uhc.com> <jVDUeZag8GA.205@forums.powersoft.com> <33B26536.FD8A07E0@uhcip6a5.uhc.com> <nP5CAMtg8GA.162@forums.powersoft.com>
Subject: Re: Starting SQL Server remotely
Date: Fri, 27 Jun 1997 06:58:01 -0400
Lines: 34
X-MimeOLE: Produced By Microsoft MimeOLE Engine V4.71.0544.0
Message-ID: <IgpbmBug8GA.162@forums.powersoft.com>
Newsgroups: sybase.public.sqlserver.nt
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.sqlserver.nt:5598
Article PK: 1081674

This is interesting: I wonder if its true for System 11 or just SQL
Anywhere???

Sybase SQL Anywhere Release 5.5.02 [release notes]
**********************************

[...]
New features
------------
New features include the following:

[...]

===========================================================
The SQL Anywhere provider now has service managing
functionality for SQL Anywhere SERVICES. This includes
creating, configuring, RUNNING, deleting, and polling.
===========================================================

... Might just be the "A" answer.

- Dave Kaufman [davidk@cnct.com]

-----------------------------------------------------
Run, rabbit, run.
Dig that hole. Forget the sun.
When at last the work is done,
Don't sit down, it's time to dig another one.
- Pink Floyd
-----------------------------------------------------


Patrick R. Sklenar Posted on 1997-06-27 12:45:33.0Z
Message-ID: <33B3B5ED.45155FD1@uhcip6a5.uhc.com>
Date: Fri, 27 Jun 1997 08:45:33 -0400
From: "Patrick R. Sklenar" <psklena@uhcip6a5.uhc.com>
Organization: United HealthCare Corp. - IT/DP&S
X-Mailer: Mozilla 4.01 [en] (WinNT; I)
MIME-Version: 1.0
Subject: Re: Starting SQL Server remotely
X-Priority: 3 (Normal)
References: <33B12950.C5D44BC3@uhcip6a5.uhc.com> <jVDUeZag8GA.205@forums.powersoft.com> <33B26536.FD8A07E0@uhcip6a5.uhc.com> <nP5CAMtg8GA.162@forums.powersoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.sqlserver.nt
Lines: 85
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.sqlserver.nt:5597
Article PK: 1081676


Dave Kaufman wrote:

> looking at it doesn't really do much; you have to read the manual

I'll pass that on to our system/network administrators. :)

Actually, I'm in the uncomfortable position of having to trust my SA's
and NA's on this. We tried to order our own copy of the Resource Kit
and were denied since it was felt that DB Product Support had no need
for OS resource tools. So I have to go by what they tell me.


> Not true. You have to be granted a single Administrative right. No
> big deal.

Which one? "Login as a Service" doesn't do it. If you can tell me
which specific one, I'll run it up my SA/NA's nose until they let me try
it. :)


> Oh well, then give up.

Not an option. At least, not the way you're implying.


> Look, if you just like UNIX, use UNIX. But if you want to give NT a
> chance, give NT a chance. ...

Hmmm ... let's see ... In production alone, I've got about 30 Unix
boxes running Sybase (compared to only about 24 UNIX boxes running
DB2/6000) and around 50 Intel boxes running NT and either MS or Sybase
DBMS's. And that's not even counting the two-hundred-plus PDC, BDC,
print, application and file servers running on NT boxes. I'd say NT's
been given a chance. The catch is ... 90% of those NT DB boxes are
running MS SQL Server, *not* Sybase. I'm trying to convince management
to switch from MS to Sybase.


> ... For instance, although every NT shop I've ever developed in had
> an administer who assigned rights and had "root" level rights
> himself, development teams were given the right to log onto the
> server locally, start and stop services,
> ...
> Rethink whether you want NT or are being forced to use it. Rethink
> whether your UNIX administrators should control the NT development
> servers if they don't know how to configure the security database.

This isn't a problem on testing and development boxes. The problem is
on production boxes. :( And, as I showed above, we've got a fair number
of them. And they're quite distributed, geographicly speaking.

The UNIX SA's have nothing to do with setting security policy ...
There's a IT team that reviews, determines and decrees security policies
for the whole corporation (35K+ employees nationwide). These policies
apply all the way from the largest MVS mainframe down to the smallest
(and oldest) i486/33 server. These policies strictly limit who has
access to System and Network Admin IDs and/or authorities.


> ... By the way, MS SQL Server has the same restrictions on starting
> and stopping services as SQL Anywhere or any other product which
> runs as an NT service.

Actually, about a year-and-a-half ago, MS has provided us with a small
utility that allows a non-SA/NA to start SQL Server related services
without requiring the user to have SA on the box. So this really isn't
an issue under MS SQL Server.

Please don't get me wrong, Dave. I'm not flaming Sybase for this. I
posted here hoping that other companies have solved this without
violating the rules I have to abide by. Sybase TS is so vastly superior
to MS's that I *REALLY* want to convert all our MS licenses to Sybase.
But I have to be able to give the Production DBA's the ability to
remotely support those production boxes too. :(

pat----

Patrick R. Sklenar
Distributed DB Product Support