Help! SQL Server 2000 extended stored procedure hangs in Windows 98

I am trying to run xp_cmdshell from the Query Analyzer using SQL
Server 2000 running on Windows 98.

It seems like it should be simple - I'm typing

xp_cmdshell 'dir *.exe'

in the Query Analyzer in the Master db. I'm logged in as sa.

The timer starts running and never stops. No error message.

Can anyone PLEASE help me with this? Any suggestions would be
appreciated. Are SQL Server 2000 extended stored procedures not
supported in Windows 98? I've tried searching the Knowledge Base but
can't find anything.

Thanks!sylmart7 (sylmart7@.aol.com) writes:
> I am trying to run xp_cmdshell from the Query Analyzer using SQL
> Server 2000 running on Windows 98.
> It seems like it should be simple - I'm typing
> xp_cmdshell 'dir *.exe'
> in the Query Analyzer in the Master db. I'm logged in as sa.
> The timer starts running and never stops. No error message.
> Can anyone PLEASE help me with this? Any suggestions would be
> appreciated. Are SQL Server 2000 extended stored procedures not
> supported in Windows 98? I've tried searching the Knowledge Base but
> can't find anything.

As I have no experience at all of Windows 98, I cannot really help. What
I can say, though, after having read the topic on xp_cmdshell in Books
Online is: yes, xp_cmdshell is supported on Win98. The article mentions
several restrictions with regards to security context and return value
on Win 98, so obviously you should be able to use it.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

help! scheduled package does nothing...

I am totally lost on this one:
I have a dts package which transforms data from tabula database into sql
server through a propriatary odbc driver.
When executed manually (through 'execute package') all is well, connection
is made to both sides
and data flows nicely.
When I schedule this package to a job it ran but nothing happaned.. Not a
single record
retrieved, nor did I get any error massage. It just vanished after 1 second
into thin air...
Both the sqlserver and the sqlserveragent services are ran by the same user
(a domain administrator) which is also the logged on user on
the sqlserver machine.
Sqlserver version is 2000 with sp installed.
The server's os is windows server 2003 enterprise edition.
Any ideas?
At this stage any suggestions will be greatly appriciated.
TIA
Rea
Rea
Have you checked that SQL Agent is running?
"Rea Peleg" <rea_p@.afek.co.il> wrote in message
news:uw18R6SLEHA.268@.TK2MSFTNGP11.phx.gbl...
> I am totally lost on this one:
> I have a dts package which transforms data from tabula database into sql
> server through a propriatary odbc driver.
> When executed manually (through 'execute package') all is well, connection
> is made to both sides
> and data flows nicely.
> When I schedule this package to a job it ran but nothing happaned.. Not a
> single record
> retrieved, nor did I get any error massage. It just vanished after 1
second
> into thin air...
> Both the sqlserver and the sqlserveragent services are ran by the same
user
> (a domain administrator) which is also the logged on user on
> the sqlserver machine.
> Sqlserver version is 2000 with sp installed.
> The server's os is windows server 2003 enterprise edition.
> Any ideas?
> At this stage any suggestions will be greatly appriciated.
> TIA
> Rea
>

help! scheduled package does nothing...

I am totally lost on this one:
I have a dts package which transforms data from tabula database into sql
server through a propriatary odbc driver.
When executed manually (through 'execute package') all is well, connection
is made to both sides
and data flows nicely.
When I schedule this package to a job it ran but nothing happaned.. Not a
single record
retrieved, nor did I get any error massage. It just vanished after 1 second
into thin air...
Both the sqlserver and the sqlserveragent services are ran by the same user
(a domain administrator) which is also the logged on user on
the sqlserver machine.
Sqlserver version is 2000 with sp installed.
The server's os is windows server 2003 enterprise edition.
Any ideas'
At this stage any suggestions will be greatly appriciated.
TIA
ReaRea
Have you checked that SQL Agent is running?
"Rea Peleg" <rea_p@.afek.co.il> wrote in message
news:uw18R6SLEHA.268@.TK2MSFTNGP11.phx.gbl...
> I am totally lost on this one:
> I have a dts package which transforms data from tabula database into sql
> server through a propriatary odbc driver.
> When executed manually (through 'execute package') all is well, connection
> is made to both sides
> and data flows nicely.
> When I schedule this package to a job it ran but nothing happaned.. Not a
> single record
> retrieved, nor did I get any error massage. It just vanished after 1
second
> into thin air...
> Both the sqlserver and the sqlserveragent services are ran by the same
user
> (a domain administrator) which is also the logged on user on
> the sqlserver machine.
> Sqlserver version is 2000 with sp installed.
> The server's os is windows server 2003 enterprise edition.
> Any ideas'
> At this stage any suggestions will be greatly appriciated.
> TIA
> Rea
>sql

Help! Removing SQLServer builtin/Administrators

Hi,
I'm having trouble maintaining security on SQLServer as
everyone who is a member of the Local Administrators (on
the system) has full control by default as SQLServer has
builtin/Administrators added by default to its System
Administrators List.
Last time I removed this group, so many things went
wrong. I dont' want the entire local administrators to be
the SQL Admins. So please suggest a way where I can
safely remove the default Built-in\Adminstrators from the
SQLServer security. Any article will be helpful.
ThanksIf you subscribe to SQL Server Professional, I wrote a piece on this:
http://www.pinpub.com/html/main.isx?sub=64&story=783
Briefly, you can add a domain account to the sysadmin role first and then
remove the BUILTIN\Administrators role.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
.
"tony" <anonymous@.discussions.microsoft.com> wrote in message
news:1475301c3c352$a5d28e00$a601280a@.phx
.gbl...
Hi,
I'm having trouble maintaining security on SQLServer as
everyone who is a member of the Local Administrators (on
the system) has full control by default as SQLServer has
builtin/Administrators added by default to its System
Administrators List.
Last time I removed this group, so many things went
wrong. I dont' want the entire local administrators to be
the SQL Admins. So please suggest a way where I can
safely remove the default Built-in\Adminstrators from the
SQLServer security. Any article will be helpful.
Thanks|||Adding to Tom's suggestion, you could also add a domain local group (with
only members you wish to have sysadmin equivalence) and grant that group
sysadmin permission -- then remove the builtin\administrators group. It's
also not a bad idea to reset the 'sa' account password at the same time in
case you need that account to log back in (in mixed mode).
Steve
"tony" <anonymous@.discussions.microsoft.com> wrote in message
news:1475301c3c352$a5d28e00$a601280a@.phx
.gbl...

quote:

---

> Hi,
> I'm having trouble maintaining security on SQLServer as
> everyone who is a member of the Local Administrators (on
> the system) has full control by default as SQLServer has
> builtin/Administrators added by default to its System
> Administrators List.
> Last time I removed this group, so many things went
> wrong. I dont' want the entire local administrators to be
> the SQL Admins. So please suggest a way where I can
> safely remove the default Built-in\Adminstrators from the
> SQLServer security. Any article will be helpful.

---

Help! Problem with DateTime.Now and SQLServer 2005

I am in the proces of upgrading from access to SQL Server 2005, and I
am having a strange problem. When I set the value a column in a data
row to DateTime.Now and save it to the server the date is two days in
the future! This happens for both typed and untyped datasets.
ex DataTable dt=new DataTable("Test")
...
DataRow row = dt.Rows[0];
row["testDate"]=DataTime.Now;
...
dbAdapter.Update(dt);
the date saved will be exactly two days in the future.
The same code worked fine with Access, also I am using the OleDb
provider for SqlServerI know this is a dumb question, but what is the date and time set to on
the SLQ Server?|||Nice thought but no dice the server date time is correct|||Hello BetaD,
A couple of quick questions:
a. You did check that the local system (where the code is running) is correc
t?
b. If you're writing .NET code, are you using SqlClient or OleDbClient? If
you're using OleDbClient, why?
c. Is the datetime off in the dataset only or does it saved incorrectly to
SQL server only or is it wrong in both places?
Thank you,
Kent Tegels
DevelopMentor
http://staff.develop.com/ktegels/sql

Help! How to give replication admin access without giving system a

Hi,
Currently we have a problem regarding security for replication. We have
a SQLServer that hosts about 30 databases. One of the database owner
requests that he needs to setup replication. But I don't want him to give
full 'system admin' rights to setup replication as he might mess up other
sqlserver settings and other databases that don't concern him. What is the
best way so that I can grant him enough access, so he can setup replication
for his database, and I don't have to worry about compromising the security
of other databases and the server.
Thanks
Hi Tony,
To administer replication through the enterprise manager you have to be a
member of the sysadmin role, and therefor have unlimited access to the whole
server.
The only way I can think of is to develop your own custom application using
SQL-DMO and/or SQL server ActiveX objects for administering a specific
replication.
see BOL, "Replication Programming"
Regards,
Jorgen D:
"Tony" wrote:

> Hi,
> Currently we have a problem regarding security for replication. We have
> a SQLServer that hosts about 30 databases. One of the database owner
> requests that he needs to setup replication. But I don't want him to give
> full 'system admin' rights to setup replication as he might mess up other
> sqlserver settings and other databases that don't concern him. What is the
> best way so that I can grant him enough access, so he can setup replication
> for his database, and I don't have to worry about compromising the security
> of other databases and the server.
> Thanks
>