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 possible? SQL Server 2000 Write times

I created an online application for one of our educational programs. The da
ta is inserted via website entry -> client side validation -> stored procedu
re -> database. Given a table stucture as follows, if 100 or even 1000 peop
le applied at the exact same time using an online application, what is the m
aximum time interval that could separate each record. How long would SQL Se
rver 2000 generally take to insert each record into the database. The probl
em is that each year, only the top 100 students are admitted in the program,
but there is one student who says they applied at 9:00 am and their record
insert time shows 9:59am. There are records before it and after it that sho
ws times like 9:58, 9:58, 9:59: 10:00, 10:00, etc. Could it really take SQL
Server 59 minutes to actually write the record if 1000 people hit the datab
ase at the same time? Please help, they want to get counsil involved.
ApplicantID int primary key identity
SSN varchar(11)
FirstName varchar(30)
LastName varchar(50)indexed
Address varchar (50)
City varchar (50)
State char (2)
Zip varchar (11)
Phone varchar (20)
Email varchar (50)
dateEntered smalldatetimeShawn Ferguson wrote:
> I created an online application for one of our educational programs.
> The data is inserted via website entry -> client side validation ->
> stored procedure -> database. Given a table stucture as follows, if 100
> or even 1000 people applied at the exact same time using an online
> application, what is the maximum time interval that could separate each
> record. How long would SQL Server 2000 generally take to insert each
> record into the database. The problem is that each year, only the top
> 100 students are admitted in the program, but there is one student who
> says they applied at 9:00 am and their record insert time shows 9:59am.
> There are records before it and after it that shows times like 9:58,
> 9:58, 9:59: 10:00, 10:00, etc. Could it really take SQL Server 59
> minutes to actually write the record if 1000 people hit the database at
> the same time? Please help, they want to get counsil involved.
> ApplicantID int primary key identity
> SSN varchar(11)
> FirstName varchar(30)
> LastName varchar(50)indexed
> Address varchar (50)
> City varchar (50)
> State char (2)
> Zip varchar (11)
> Phone varchar (20)
> Email varchar (50)
> dateEntered smalldatetime
I would not expect that sort of delay. 9:00am/9:59am, could there be a
time zone discrepancy? Can you use your website logs to determine when
the user made their submission?

Is this possible? Monitor replication from VB 6.0

I have a client with approximately 30 laptops all running SQL Server
2000 (databse is about 13 gigabytes, this is _not_ MSDE). They have a
legacy application written in VB 6.0.
The decision has been made to change their replication model.
Replication between a "central" SQL Server database and the laptops
used to be triggered through the application whenever the laptop user
chose to. Now they are going to use a two-part method, so that the
user's logs are replicated whenever they connect to the central server,
and product data (which can be huge) will be scheduled in stages
overnight. The VB application will have no control over when they
replicate. The logs will use Merge replication and the product data
will use Transactional replication.
The problem is they expect the application to continue to monitor the
replication "progress" in both scenarios. I have gotten them to accept
that their progress bars will go away, that there will only be an item
in their status bars that it is running (or not).
I have figured out a way to monitor that Merge replication is going on
by watching the MSmerge_history and MSmerge_agents tables in the
Distribution database, but I am not sure that even this will continue
to work once the laptops stop using the ActiveX MS SQL Merge Control to
trigger replication, and it will not work at all for Transactional
replication.
Does anyone have a way (or have a suggestion that might lead to a way)
as to how I can tell from VB whether replication is in progress against
the local SQL Server database? If you believe this is impossible, I
would appreciate hearing that as well.
Thanks,
Austin
Have you looked at the status event?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"AustinMN" <tacooper260@.hotmail.com> wrote in message
news:1126531606.616225.228610@.g14g2000cwa.googlegr oups.com...
> I have a client with approximately 30 laptops all running SQL Server
> 2000 (databse is about 13 gigabytes, this is _not_ MSDE). They have a
> legacy application written in VB 6.0.
> The decision has been made to change their replication model.
> Replication between a "central" SQL Server database and the laptops
> used to be triggered through the application whenever the laptop user
> chose to. Now they are going to use a two-part method, so that the
> user's logs are replicated whenever they connect to the central server,
> and product data (which can be huge) will be scheduled in stages
> overnight. The VB application will have no control over when they
> replicate. The logs will use Merge replication and the product data
> will use Transactional replication.
> The problem is they expect the application to continue to monitor the
> replication "progress" in both scenarios. I have gotten them to accept
> that their progress bars will go away, that there will only be an item
> in their status bars that it is running (or not).
> I have figured out a way to monitor that Merge replication is going on
> by watching the MSmerge_history and MSmerge_agents tables in the
> Distribution database, but I am not sure that even this will continue
> to work once the laptops stop using the ActiveX MS SQL Merge Control to
> trigger replication, and it will not work at all for Transactional
> replication.
> Does anyone have a way (or have a suggestion that might lead to a way)
> as to how I can tell from VB whether replication is in progress against
> the local SQL Server database? If you believe this is impossible, I
> would appreciate hearing that as well.
> Thanks,
> Austin
>
|||Hilary Cotter wrote
> Have you looked at the status event?
Yes, I have. The Status event applies to the ActiveX replication
components, whicb are being removed from the application. It only reports
on replication started by the components, so is useless for replication
initiated by the Distributor/Publisher database.
Austin
You programmed with 1s and 0s? We only had 0s!
There are no X characters in my address
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "AustinMN" <tacooper260@.hotmail.com> wrote in message
> news:1126531606.616225.228610@.g14g2000cwa.googlegr oups.com...
>
|||"AustinMN" <tacooper260@.hotmail.com> wrote in message
news:1126531606.616225.228610@.g14g2000cwa.googlegr oups.com...
>I have a client with approximately 30 laptops all running SQL Server
> The problem is they expect the application to continue to monitor the
> replication "progress" in both scenarios. I have gotten them to accept
> that their progress bars will go away, that there will only be an item
> in their status bars that it is running (or not).
> I have figured out a way to monitor that Merge replication is going on
> by watching the MSmerge_history and MSmerge_agents tables in the
> Distribution database, but I am not sure that even this will continue
> to work once the laptops stop using the ActiveX MS SQL Merge Control to
> trigger replication, and it will not work at all for Transactional
> replication.
> Does anyone have a way (or have a suggestion that might lead to a way)
> as to how I can tell from VB whether replication is in progress against
> the local SQL Server database? If you believe this is impossible, I
> would appreciate hearing that as well.
>
My experience is with Oracle. With Oracle Enterprise Manager, you can see a list
of current connections (which I do fairly often), and you can see lists or logs
of recent changes (which I don't do much). It seems like there would have to be
something similar in SQL Server. Activity at the level of replication can't be
completely hidden. It is just a matter of finding out which thing to look
for...Maybe you could even detect the running process on the laptop with an API
call?

Is this a 'dirty read'?

Hello,

trying to understand the concepts of isolation levels not understanding it completely this is my question:

Client A and client B both are querying the same database.
Situation:
- client B starts a transactional operation
- client A executes a non-transactional read operation
- client B rolls back his transactional operation

Is the non-transactional read operation executed by client A called
a 'dirty read'? Or do isolation levels always apply to at least two
clients executing BOTH transactional operations?

regards,
HenkProbably not...depending on if you are using the READUNCOMMITTED isolation level. A dirty read occurs when transactionA starts, updates data, and TransactionB issues a read against a what transactionA is modifiying and transactionB does not issue shared locks against that table when reading it. If transA rolls it work back, transB has read dirty data. Here is an example:

TransA:
BEGIN TRAN
INSERT INTO TableA VALUES('A')

TransB:
SELECT * FROM TableA WITH(NOLOCK)

TransA:
ROLLBACK TRAN

TransB will have read the row that was rolled back from the database, and thus a dirty read.

Hope this helps,
Tim

is there anyway to raise a warning from a UDF (in sql2000 and/or in SQL2005)

cos RAISERROR isnt callable, but I really want to indicate a non-fatal warning to be passed back to the client (C++ code)

You are limited to a single output either way dealing with a scalar or table valued function. The only way you could pass back a message of some sort would be to overwrite the scalar return value or add a column to your table return. Neither of those sound particulary appealing but you have few options.|||In SQL Server 2005, you could replace the TSQL UDF with CLR UDF and raise exception in your CLR code. But this is not a pretty implementation and depending on the TSQL code you will get worse performance. So best is to modify the UDF to a SP or just check for absence of row or special value like NULL.

Is there any requirement to install the client component of RS?

Hi all,
I only install the client component of reporting service,
at the beginning, when it is install the support file, it
always failed with only an 'error' message. No other
messages.
I check the log file. There is
Internet Information Services 5.0 (IIS) or later is either
not installed, or it is configured in a way that is
incompatible with a Reporting Services installation.
ASP.NET version 1.1 is not installed or is not registered
with your Web server. ASP.Net is required for the Report
Server and the Report Manager components.
and in the stlog file, I notice
<Prerequisite Name="IsIISInstalled" Checked="Metabase"
Item="/" Found="Can not open metabase" Expected="No error"
Result="Fail" />
To only install the client component, should I install IIS
and ASP1.1 and how do I check that every thing is OK to
install it.
Thanks.
Lindayou need Visual studio.Net 2003 and .Net framework 1.1
IIS is not required
"YUKON2005" <anonymous@.discussions.microsoft.com> a écrit dans le message de
news:38d201c471e9$c199d760$a501280a@.phx.gbl...
> Hi all,
> I only install the client component of reporting service,
> at the beginning, when it is install the support file, it
> always failed with only an 'error' message. No other
> messages.
> I check the log file. There is
> Internet Information Services 5.0 (IIS) or later is either
> not installed, or it is configured in a way that is
> incompatible with a Reporting Services installation.
> ASP.NET version 1.1 is not installed or is not registered
> with your Web server. ASP.Net is required for the Report
> Server and the Report Manager components.
> and in the stlog file, I notice
> <Prerequisite Name="IsIISInstalled" Checked="Metabase"
> Item="/" Found="Can not open metabase" Expected="No error"
> Result="Fail" />
> To only install the client component, should I install IIS
> and ASP1.1 and how do I check that every thing is OK to
> install it.
> Thanks.
> Linda
>|||Thank you!
I will check it.
:)