Our Application dosn't work with Sql Service pack 3

Hi , My name is Tomas
I work for a Software Developing Company ,
Our applications has been written and developed by
Power Builder 5.0 , and they can work with Sql Server 2000
normally , but when I install service pack 3.0 on our sql
server after that our application can't work with sql
server correctly , for example some queries doesn't run
and there is no result for them after installing service
pack 3,,
Please Help MeHi
First thing you need to do is run profiler on the server to see what queries
are being submitted. then pick some of those queries and run them in Query
Analyzer. In that situation, you will be able to tell if your code is
running with errors.
If your application is using more than 1 database at the same time, look at
the "Cross-Database Ownership Chaining" in books online. This was a change
introduced by SP3.
--
--
Mike Epprecht, Microsoft SQL Server MVP
Epprecht Consulting (PTY) LTD
Johannesburg, South Africa
Mobile: +27-82-552-0268
IM: mike@.NOSPAMepprecht.net
Specialist SQL Server Solutions and Consulting
"Tomas" <anonymous@.discussions.microsoft.com> wrote in message
news:01a101c3d429$41ba6c70$a001280a@.phx.gbl...
> Hi , My name is Tomas
> I work for a Software Developing Company ,
> Our applications has been written and developed by
> Power Builder 5.0 , and they can work with Sql Server 2000
> normally , but when I install service pack 3.0 on our sql
> server after that our application can't work with sql
> server correctly , for example some queries doesn't run
> and there is no result for them after installing service
> pack 3,,
> Please Help Me
>|||you should really consider upgrading powerbuilder. when did 5.0 come
out, the mid 90's?
Tomas wrote:
> Hi , My name is Tomas
> I work for a Software Developing Company ,
> Our applications has been written and developed by
> Power Builder 5.0 , and they can work with Sql Server 2000
> normally , but when I install service pack 3.0 on our sql
> server after that our application can't work with sql
> server correctly , for example some queries doesn't run
> and there is no result for them after installing service
> pack 3,,
> Please Help Me|||Especially since PB5 is no longer supported much less supported for use with
SQL2000. We're using PB9 and it works great with SQL2K.
Mike Kruchten
"ch" <ch@.dontemailme.com> wrote in message
news:3FFB0C2E.A65CF347@.dontemailme.com...
> you should really consider upgrading powerbuilder. when did 5.0 come
> out, the mid 90's?
>
> Tomas wrote:
> > Hi , My name is Tomas
> > I work for a Software Developing Company ,
> > Our applications has been written and developed by
> > Power Builder 5.0 , and they can work with Sql Server 2000
> > normally , but when I install service pack 3.0 on our sql
> > server after that our application can't work with sql
> > server correctly , for example some queries doesn't run
> > and there is no result for them after installing service
> > pack 3,,
> > Please Help Me
>

OS Service pack

Is there a way from within a SQL Script to determine what OS service
pack is installed other than SELECT @.@.VERSION? I am trying to
automate a script based upon the OS service pack installed (if any),
and having to somehow parse the results of @.@.VERSION seems unreliable.
Any ideas?
Brandon
--
"In the beginning the universe was created. This has made a lot of
people very angry, and has been widely regarded as a bad move." -
Douglas Noel Adams (1952-2001)Have a look at SERVERPROPERTY and xp_msver.
Off the top of my head I think you need to run :- xp_msver windowsversion
--
HTH
Ryan Waight, MCDBA, MCSE
"Brandon Lilly" <brandon.lilly@.nospam_medevolve.com> wrote in message
news:eZw5EB3kDHA.3612@.TK2MSFTNGP11.phx.gbl...
> Is there a way from within a SQL Script to determine what OS service
> pack is installed other than SELECT @.@.VERSION? I am trying to
> automate a script based upon the OS service pack installed (if any),
> and having to somehow parse the results of @.@.VERSION seems unreliable.
> Any ideas?
> Brandon
> --
> "In the beginning the universe was created. This has made a lot of
> people very angry, and has been widely regarded as a bad move." -
> Douglas Noel Adams (1952-2001)
>|||You can get the OS information by running the
xp_msver 'WindowsVersion' extended stored procedure.
Like so...
CREATE TABLE #windows_info
(
idx INT
, name NVARCHAR(128)
, internal_value INT
, character_value NVARCHAR(255)
)
INSERT #windows_info
EXECUTE xp_msver 'WindowsVersion'
SELECT * FROM #windows_info
I don't know if this is easier than parsing the @.@.VERSION
string though.
Tim
>--Original Message--
>Is there a way from within a SQL Script to determine
what OS service
>pack is installed other than SELECT @.@.VERSION? I am
trying to
>automate a script based upon the OS service pack
installed (if any),
>and having to somehow parse the results of @.@.VERSION
seems unreliable.
>Any ideas?
>Brandon
>--
>"In the beginning the universe was created. This has
made a lot of
>people very angry, and has been widely regarded as a bad
move." -
>Douglas Noel Adams (1952-2001)
>
>.
>|||You can get it from the registry, using the undocumented
xp_regread. Try:
exec
master..xp_regread 'HKEY_LOCAL_MACHINE', 'SOFTWARE\Microsof
t\Windows NT\CurrentVersion', 'CSDVersion'
If your OS is NT 4, this won't distinguish between SP6 and
SP6a.
HTH
Vern
>--Original Message--
>Is there a way from within a SQL Script to determine what
OS service
>pack is installed other than SELECT @.@.VERSION? I am
trying to
>automate a script based upon the OS service pack
installed (if any),
>and having to somehow parse the results of @.@.VERSION
seems unreliable.
>Any ideas?
>Brandon
>--
>"In the beginning the universe was created. This has
made a lot of
>people very angry, and has been widely regarded as a bad
move." -
>Douglas Noel Adams (1952-2001)
>
>.
>