Is this the bug in SQL2000?

HI Group
I have shared memory enable on client network utility
on my sql2000 server but every time I restart the service
I will lost my setting even the box still check enable
shared memory but my sql only listen to TCP and Name pipe
Does any one have this same problem ? I must restart the
sql service 4 to 5 times before the sql server listen to
the share memory. Any clue ?
ThanksThe "Client Network Utility" is only used to configure how clients connect.
The "Server Network Utility" controls what connections SQL Server will
accept/listen on. It does not have an option for shared memory, that is
always on unless there is a failure at startup (which would be documented
in the SQL error log).
Which utility are you using? Where are you checking what SQL Server listens
on (check the SQL error log)? What is the actual failure you see?
Hint: To force a client to connect with a certain protocol, include it in
the connection string. If your instance name is MyServer\Inst1, you would
use:
for TCP/IP sockets: tcp:MyServer\Inst1
for shared memory: lcp:MyServer\Inst1
for named pipes: np:MyServer\Inst1
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||HI
I checked in the error log when SQL started
the only TCP and Namepipe is listen by server
then if I use query analyzer on the console
it will connect at TCP protocol
I wolud like to connect client from sql console
using LPC protocol not TCP. Again there is no error
indicated any thing failed on sql startup log but
it only listen to TCP and Name pipe even shared memory
have been checked.
Thanks
>--Original Message--
>The "Client Network Utility" is only used to configure
how clients connect.
>The "Server Network Utility" controls what connections
SQL Server will
>accept/listen on. It does not have an option for shared
memory, that is
>always on unless there is a failure at startup (which
would be documented
>in the SQL error log).
>Which utility are you using? Where are you checking what
SQL Server listens
>on (check the SQL error log)? What is the actual failure
you see?
>Hint: To force a client to connect with a certain
protocol, include it in
>the connection string. If your instance name is
MyServer\Inst1, you would
>use:
>for TCP/IP sockets: tcp:MyServer\Inst1
>for shared memory: lcp:MyServer\Inst1
>for named pipes: np:MyServer\Inst1
>Cindy Gross, MCDBA, MCSE
>http://cindygross.tripod.com
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>.
>|||There is no checkbox to make SQL Server listen on shared memory. I suspect
you're talking about the checkbox that allows a client to connect with
shared memory. Shared memory only works on the same box.
You mentioned that SQL Server is only listening on TCP and named pipes. If
the error log doesn't list shared memory as a protocol it is listening on
then you should check to see if there are other errors, particularly
related to ssnetlib.dll. Can you post your errorlog file?
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.sql

is this the best way to backup more than one database

I am setting up a DTS so that we can backup each of the database, is this the best way to back up each of the mdf & ldf files to another server? cheers

EXEC sp_addumpdevice 'disk', 'cc_150_chg', '\\homer\db_backups$\cc_150_chg.mdf'
EXEC sp_addumpdevice 'disk', 'cc_150_chg_admin', '\\homer\db_backups$\cc_150_chg_admin.mdf'
EXEC sp_addumpdevice 'disk', 'cc_150_chg_Log', '\\homer\db_backups$\cc_150_chg_log.ldf'
EXEC sp_addumpdevice 'disk', 'cc_150_chg_admin_log', '\\homer\db_backups$\cc_150_chg_admin.ldf'
EXEC sp_addumpdevice 'disk', 'cc_153', '\\homer\db_backups$\cc_153.mdf'
EXEC sp_addumpdevice 'disk', 'cc_153_log', '\\homer\db_backups$\cc_153.ldf'
EXEC sp_addumpdevice 'disk', 'cc_153_admin', '\\homer\db_backups$\cc_153_admin.mdf'
EXEC

This will form part of the step in 'command line'?

Cheers
EWhy don't you just backup to a file?|||backup all the database to a file? How can I do this? also do i need to specifiy all the databases individually by backuping both mdf & ldf files?|||Backup each database to a separate file. You don't need to back up the log files (ldf) unless you need point-in-time restore.|||You don't need to back up the log files (ldf)

You're fired|||alll sorted!!!!1thanx|||OK Brett, YOU explain the whole concept of log files to him! I got actual work I gotta do today.

...or just point him to Books Online...

:)|||OK Brett, YOU explain the whole concept of log files to him! I got actual work I gotta do today.

...or just point him to Books Online...

:)

Settle down...

Hey, there's a first time for everything, too

OR, I could just post Tara's blog

http://weblogs.sqlteam.com/tarad/category/95.aspx

I think I've stolen most of that...

Let me ask...when was the last time, aside from testing contingency, that you had to do a restore, and have to reapply all of the logs?

I don't remeber...had to be 6.5

Is this a hack? Is it bad news for me?

Sorry if this is elementary, but while I've been using SQL7 and SQL2000 for quite a while, I'm new to setting up a server.

I am setting up a new testing server, with WinXP Pro and SQLServer2000, amongst other things. After a day or so of tinkering with it, I noticed that when I was offline, (my broadband wont be installed until late Jan, so I'm using a dialup in the mean time) the machine would just start dialling my isp all by itself, including in the middle of the night, when I most definitely have NOT been doing anything on the system. Trying to trace the source of this activity, I have seen in the event viewer that there's a lot of activity in my SQL2000.

I'm particularly interested in a number of items labeled

8128 :
Using 'xpsqlbot.dll' version '2000.80.194' to execute extended stored procedure 'xp_qv'.

These have run at a time when I have been in bed asleep and certainly not doing anything on my system. I haven't set up any stored procedures myself yet - this is a brand new SQL2000 installation and hasn't got any live data on it yet.

I'm thinking this is a hack attempt (probably successful). Is there any legitimate reason why SQL2000 should be active when nothing else is on my system? Since this is (or at least WAS) a default installation, is there anything called xp_qv that has a legitimate use?

Should I be suspecting a hack if it's SQL2000 that's trying to dial out to the internet all the time? How else can i find out what's doing it? (All the entries in the WinXP event viewer at this time are related to SQL2000.)

Cheers,
Michael Kear
Windsor, NSW, Australia
AFP Webworks.master.dbo.xp_qv is undocumented Microsoft XP
I heard it can be used to find installation type
of SQL Server. No more data ...|||Originally posted by ispaleny
master.dbo.xp_qv is undocumented Microsoft XP
I heard it can be used to find installation type
of SQL Server. No more data ...

So does anyone know how I can find out why SQLServer2000 is waking up at all hours and trying to connect to my isp? Or indeed if it's not SQLServer but something else?

The event viewer shows only SQLServer activity at those hours and now that I have disabled SQLServer, the computer is no longer trying to connect to the internet.

What could be causing this behaviour? I dont want my system just connecting up to the net when it feels like it.

Cheers
Mike Kear
AFP Webworks
Windsor, NSW, Australia.|||MSSQLSERVER can be really used to perform attack on server. There are many SPs and XPs
which can run programs or call COM objects, but I have never seen such an attack yet.

I think, that your server is just badly configured, probably at network level.
MSSQLSERVER is only pinging connection and this is detected as I-net access.|||Turn it off when you're not using it!!