Pauses in SQL 2000

I am running SQL 2000 SP3 on a Windows 2003 server. I am
having problems with pauses in my application software. I
put a protocol analyzer on the switch and I am getting no
data error but I am getting a large amount of SQL
retries. It this normal? Has anyone seen this problem
before?
Thanks,
Jason Mobley
Technology Director
NWFL Daily NewsRetries sound like client connection issues. What I would do is try and
isolate a client machine, and see if you could load SQL client tools. Then
you could run SQL Client Network Utiltiy and compare it to SQL Server
Network Utility on the server. Sometimes the TCP/IP sockets port gets
changed from the default port of 1433, or firewalls block it. In that case,
the clients will switch from TCP/IP sockets to Named Pipes, or conceivably
keep trying to connect. I would investigat that. Even though Named Pipes
seems to be a default, I've seen a lot of clients out there default to
TCP/IP sockets, especially when going to ODBC Data Sources in control panel
and configuring a SQL Server System DSN (client configuration on the login
credential screen shows you what is being used for connections as well).
Read this article for information on Named Pipes and TCP/IP sockets
http://msdn.microsoft.com/library/d.../>
1a_7fcj.asp
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"Jmobley" <anonymous@.discussions.microsoft.com> wrote in message
news:6e1801c3e75a$3c080fa0$a301280a@.phx.gbl...

quote:

---

> I am running SQL 2000 SP3 on a Windows 2003 server. I am
> having problems with pauses in my application software. I
> put a protocol analyzer on the switch and I am getting no
> data error but I am getting a large amount of SQL
> retries. It this normal? Has anyone seen this problem
> before?
> Thanks,
> Jason Mobley
> Technology Director
> NWFL Daily News
>

---

PATINDEX and [ character

Hi all

Using SQL Server 2000 SP3 on WIn2K Pro with SP2.

When I do this

SELECT PATINDEX('%[%', 'ABC[DEF')
GO

I get a result of 0, when I would expect a result of 4.

This works as I expect:

SELECT PATINDEX('%]%', 'ABC]DEF')
GO

I must be missing something really obvious here Any help would be
appreciated.John Winterbottom (john_winterbottom@.hotmail.com) writes:
> Using SQL Server 2000 SP3 on WIn2K Pro with SP2.
> When I do this
> SELECT PATINDEX('%[%', 'ABC[DEF')
> GO
> I get a result of 0, when I would expect a result of 4.

[ is meta-character in wildcard expressions. You need this:

SELECT PATINDEX('%[[]%', 'ABC[DEF')
GO

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

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||The \ character is not an escape character until you define it as the
escape character. This is possible when using LIKE, but there is not
such ESCAPE clause in the PATINDEX syntax.

Therefore, you will need to resort to the second syntax, which is to
enclose it as the only character between square brackets.

SELECT PATINDEX('%[[]%', 'ABC[DEF')

Hope this helps,
Gert-Jan

John Winterbottom wrote:
> "Joseph Weinstein" <joe@.bea.com> wrote in message
> news:3F426D21.DB095501@.bea.com...
> > John Winterbottom wrote:
> > > Hi all
> > > > Using SQL Server 2000 SP3 on WIn2K Pro with SP2.
> > > > When I do this
> > > > SELECT PATINDEX('%[%', 'ABC[DEF')
> > > GO
> > > > I get a result of 0, when I would expect a result of 4.
> > > > This works as I expect:
> > > > SELECT PATINDEX('%]%', 'ABC]DEF')
> > > GO
> > > > I must be missing something really obvious here Any help would be
> > > appreciated.
> > Hi. I think the '[' is syntactically significant, and is parsed out of the
> input pattern,
> > just like the '%' is. Try escaping the '[' like this:
> > SELECT PATINDEX('%\[%', 'ABC[DEF')
> > This is just as if you wanted to search a pattern for the literal '%', you
> would
> > have to escape that... Lemme know...
> > Joe
> Thanks for the help Joe. Still doesn't work, even with the escape character.
> Yes, i think you are right - it must be interpreting the '[' character and
> stripping it out. If I come up with a fix I'll let you know.|||"Gert-Jan Strik" <sorry@.toomuchspamalready.nl> wrote in message
news:3F42865B.C1FF0C4D@.toomuchspamalready.nl...
> The \ character is not an escape character until you define it as the
> escape character. This is possible when using LIKE, but there is not
> such ESCAPE clause in the PATINDEX syntax.
> Therefore, you will need to resort to the second syntax, which is to
> enclose it as the only character between square brackets.
> SELECT PATINDEX('%[[]%', 'ABC[DEF')
> Hope this helps,
> Gert-Jan

Perfect - thank you.|||"Erland Sommarskog" <sommar@.algonet.se> wrote in message
news:Xns93DCDFC6B245EYazorman@.127.0.0.1...
> John Winterbottom (john_winterbottom@.hotmail.com) writes:
> > Using SQL Server 2000 SP3 on WIn2K Pro with SP2.
> > When I do this
> > SELECT PATINDEX('%[%', 'ABC[DEF')
> > GO
> > I get a result of 0, when I would expect a result of 4.
> [ is meta-character in wildcard expressions. You need this:
> SELECT PATINDEX('%[[]%', 'ABC[DEF')
> GO

Thanks veyr much for your help. This works fine now.

Patching SQL in a Clustered Environment

We are running a SQL within an Active Active Windows
Cluster setup. Will I run into any issues when attempting
to patch SQL with SQL SP3? Are there any issues I should
be aware of when patching the SQL cluster or any
prerequisite patches that need to be applied before
patching SQL in a cluster?
This is a rather open ended question. Are you talking about a specific
patch or just patches in general
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||I am speaking of a general Serivce Pack 3a update. When dealing with virtual servers, are there any issues when applying the SP3a update?
rp
-- Rand Boyd [MSFT] wrote: --
This is a rather open ended question. Are you talking about a specific
patch or just patches in general
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Not really anything special. Make sure all nodes are online and are capable
of hosting the service. You will need to run the service pack from the node
hosting the particular instance you wish to update. If you have more than
one instance, you will need to apply the Service Pack to each instance
independantly. It is possible to run different instances at different
service pack and hotfix levels without a problem. Of course all instances
on a particular host will run against the same level MDAC installation. If
you run into any issues, you know where to find help.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Bob" <anonymous@.discussions.microsoft.com> wrote in message
news:02068577-4EB9-472E-A36E-D21EF109FC91@.microsoft.com...
> I am speaking of a general Serivce Pack 3a update. When dealing with
virtual servers, are there any issues when applying the SP3a update?
> rp
> -- Rand Boyd [MSFT] wrote: --
> This is a rather open ended question. Are you talking about a
specific
> patch or just patches in general
> Rand
> This posting is provided "as is" with no warranties and confers no
rights.
>
|||Before applying any service pack, always review the readme. For sp3a on a
cluster, see:
811168 INF: SQL Server 2000 Service Pack 3 or Service Pack 3a
Pre-Installation
http://support.microsoft.com/?id=811168
And you should strongly consider applying the MS03-031 security rollup as
well.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi Cindy. I didn't know you had joined Microsoft.
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com

patch application procedure

Hi,
I am having an mssql server with sp3. It is in sql cluster
(NT) as well as it participates in replication (merge). My
comany is very paranoid about doing things and all the
more there is no testing environment. Could any one please
explain how to apply SP4 for this server? We need to
consider the problematic conditions and disaster recovery
as well. My recovery mode is set to full.
james bond...-- james bond wrote: --
> Hi,
>> I am having an mssql server with sp3. It is in sql cluster
> (NT) as well as it participates in replication (merge). My
> company is very paranoid about doing things and all the
> more there is no testing environment. Could any one please
> explain how to apply SP4 for this server? We need to
> consider the problematic conditions and disaster recovery
> as well. My recovery mode is set to full.
--
Hi James Bond,
The best source of information for a service pack install is the README.htm of the service pack itself.
Hope this helps,
-Eric Cárdenas
SQL Server support

patch / update which packages?

hi
i updated my sql server today to sp3
there are more packages to download from microsoft site
the analysis package and the
msde desktop engine
do i need those too to have a full patched and updated sql server ready?
thank you for your hints
mike schwarzIf you are running analysis services then you need the analysis package.
If you are utilizing msde then you need the msde package. Otherwise you are
ok.
"Mike Schwarz" <ctek@.ctek.ch> wrote in message
news:ejyoWTBHEHA.2768@.tk2msftngp13.phx.gbl...
> hi
> i updated my sql server today to sp3
> there are more packages to download from microsoft site
> the analysis package and the
> msde desktop engine
> do i need those too to have a full patched and updated sql server ready?
> thank you for your hints
> mike schwarz
>
>