Showing posts with label version. Show all posts
Showing posts with label version. Show all posts

Monday, March 19, 2012

bad performance due to drivers?

Do you know if there are any performance issues using a sql server 3.70 driver on an application server versus using a 2000 version driver? The DB is on a server with SQL Server 2000 EE. We have four application servers and 2 have 2000 drivers (and window
s SP4) and the other 2 have 3.70 drivers (and windows SP3) and the ones with the 3.70 drivers keep getting timeouts. CPU and memory usage doesn't seem very high - does anyone know what else to monitor to see what could be affecting performance? Thanks.
One way to analyze the performance issues in your 7.0 environment would be
to enable SQL Server profiler and capture the execution plan, show plan
statistics, Started and completed events for RPC, SQL and Batch. We can
compare the results to SQL 2000.
Other factors (other than drivers) that could contribute to the
differences in the performance in the two environments are;
- SQL Server 2000 vs 7.0
- Data differences in the two environments
- Application differences
- Maybe network related issues
If you require assistance in analyzing the profiler data please contact
Microsoft Support.
HTH
Agnes Panosian
SQL Server Support
|||Here are some references that may also help
http://msdn.microsoft.com/library/de...us/dnsql7/html
/msdn_sql7perftune.asp
KB articles
INF: Job to Monitor SQL Server 7.0 Performance and Activity ID: 286191
HOW TO: Troubleshoot Application Performance with SQL Server ID: 224587
INF: How to Monitor SQL Server 7.0 Blocking ID: 251004.

bad performance due to drivers?

Do you know if there are any performance issues using a sql server 3.70 driver on an application server versus using a 2000 version driver? The DB is on a server with SQL Server 2000 EE. We have four application servers and 2 have 2000 drivers (and windows SP4) and the other 2 have 3.70 drivers (and windows SP3) and the ones with the 3.70 drivers keep getting timeouts. CPU and memory usage doesn't seem very high - does anyone know what else to monitor to see what could be affecting performance? Thanks.One way to analyze the performance issues in your 7.0 environment would be
to enable SQL Server profiler and capture the execution plan, show plan
statistics, Started and completed events for RPC, SQL and Batch. We can
compare the results to SQL 2000.
Other factors (other than drivers) that could contribute to the
differences in the performance in the two environments are;
- SQL Server 2000 vs 7.0
- Data differences in the two environments
- Application differences
- Maybe network related issues
If you require assistance in analyzing the profiler data please contact
Microsoft Support.
HTH
Agnes Panosian
SQL Server Support|||Here are some references that may also help
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql7/html
/msdn_sql7perftune.asp
KB articles
INF: Job to Monitor SQL Server 7.0 Performance and Activity ID: 286191
HOW TO: Troubleshoot Application Performance with SQL Server ID: 224587
INF: How to Monitor SQL Server 7.0 Blocking ID: 251004.

bad performance due to drivers?

Do you know if there are any performance issues using a sql server 3.70 driv
er on an application server versus using a 2000 version driver? The DB is on
a server with SQL Server 2000 EE. We have four application servers and 2 ha
ve 2000 drivers (and window
s SP4) and the other 2 have 3.70 drivers (and windows SP3) and the ones with
the 3.70 drivers keep getting timeouts. CPU and memory usage doesn't seem v
ery high - does anyone know what else to monitor to see what could be affect
ing performance? Thanks.One way to analyze the performance issues in your 7.0 environment would be
to enable SQL Server profiler and capture the execution plan, show plan
statistics, Started and completed events for RPC, SQL and Batch. We can
compare the results to SQL 2000.
Other factors (other than drivers) that could contribute to the
differences in the performance in the two environments are;
- SQL Server 2000 vs 7.0
- Data differences in the two environments
- Application differences
- Maybe network related issues
If you require assistance in analyzing the profiler data please contact
Microsoft Support.
HTH
Agnes Panosian
SQL Server Support|||Here are some references that may also help
http://msdn.microsoft.com/library/d...-us/dnsql7/html
/msdn_sql7perftune.asp
KB articles
INF: Job to Monitor SQL Server 7.0 Performance and Activity ID: 286191
HOW TO: Troubleshoot Application Performance with SQL Server ID: 224587
INF: How to Monitor SQL Server 7.0 Blocking ID: 251004.

Sunday, February 19, 2012

Backup/Restore Problem

I have a SQL 2000 Server that I want to create a test version of a database
on another SQL 2000 server. After creating a backup (database – complete) of
the desired database and attempting a restore on a dev server (creating a new
db name on the dev server), it fails with a consistency error. The log
contains the following message: 3266 :The backup data in 'D:\PPTest' is
incorrectly formatted. Backups cannot be appended, but existing backup sets
may still be usable. I have run dbcc checkdb checks on the source db and
they seem ok. Any ideas why I am getting this error on the restore?
Hi
Did you back this up to a tape or to disc?
Does this help?
http://msdn2.microsoft.com/en-us/library/aa238258(SQL.80).aspx
John
"TC" wrote:

> I have a SQL 2000 Server that I want to create a test version of a database
> on another SQL 2000 server. After creating a backup (database – complete) of
> the desired database and attempting a restore on a dev server (creating a new
> db name on the dev server), it fails with a consistency error. The log
> contains the following message: 3266 :The backup data in 'D:\PPTest' is
> incorrectly formatted. Backups cannot be appended, but existing backup sets
> may still be usable. I have run dbcc checkdb checks on the source db and
> they seem ok. Any ideas why I am getting this error on the restore?
|||I am having the same problem. I am backing it up to disk on another server.
Thanks
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Did you back this up to a tape or to disc?
> Does this help?
> http://msdn2.microsoft.com/en-us/library/aa238258(SQL.80).aspx
> John
> "TC" wrote:
|||Hi
If you back up locally you can run RESTORE VERIFYONLY to check it is ok
before moving it.
John
"Agho" wrote:
[vbcol=seagreen]
> I am having the same problem. I am backing it up to disk on another server.
> Thanks
>
> "John Bell" wrote:

Backup/Restore Problem

I have a SQL 2000 Server that I want to create a test version of a database
on another SQL 2000 server. After creating a backup (database â' complete) of
the desired database and attempting a restore on a dev server (creating a new
db name on the dev server), it fails with a consistency error. The log
contains the following message: 3266 :The backup data in 'D:\PPTest' is
incorrectly formatted. Backups cannot be appended, but existing backup sets
may still be usable. I have run dbcc checkdb checks on the source db and
they seem ok. Any ideas why I am getting this error on the restore?Hi
Did you back this up to a tape or to disc?
Does this help?
http://msdn2.microsoft.com/en-us/library/aa238258(SQL.80).aspx
John
"TC" wrote:
> I have a SQL 2000 Server that I want to create a test version of a database
> on another SQL 2000 server. After creating a backup (database â' complete) of
> the desired database and attempting a restore on a dev server (creating a new
> db name on the dev server), it fails with a consistency error. The log
> contains the following message: 3266 :The backup data in 'D:\PPTest' is
> incorrectly formatted. Backups cannot be appended, but existing backup sets
> may still be usable. I have run dbcc checkdb checks on the source db and
> they seem ok. Any ideas why I am getting this error on the restore?|||I am having the same problem. I am backing it up to disk on another server.
Thanks
"John Bell" wrote:
> Hi
> Did you back this up to a tape or to disc?
> Does this help?
> http://msdn2.microsoft.com/en-us/library/aa238258(SQL.80).aspx
> John
> "TC" wrote:
> > I have a SQL 2000 Server that I want to create a test version of a database
> > on another SQL 2000 server. After creating a backup (database â' complete) of
> > the desired database and attempting a restore on a dev server (creating a new
> > db name on the dev server), it fails with a consistency error. The log
> > contains the following message: 3266 :The backup data in 'D:\PPTest' is
> > incorrectly formatted. Backups cannot be appended, but existing backup sets
> > may still be usable. I have run dbcc checkdb checks on the source db and
> > they seem ok. Any ideas why I am getting this error on the restore?|||Hi
If you back up locally you can run RESTORE VERIFYONLY to check it is ok
before moving it.
John
"Agho" wrote:
> I am having the same problem. I am backing it up to disk on another server.
> Thanks
>
> "John Bell" wrote:
> > Hi
> >
> > Did you back this up to a tape or to disc?
> >
> > Does this help?
> > http://msdn2.microsoft.com/en-us/library/aa238258(SQL.80).aspx
> >
> > John
> >
> > "TC" wrote:
> >
> > > I have a SQL 2000 Server that I want to create a test version of a database
> > > on another SQL 2000 server. After creating a backup (database â' complete) of
> > > the desired database and attempting a restore on a dev server (creating a new
> > > db name on the dev server), it fails with a consistency error. The log
> > > contains the following message: 3266 :The backup data in 'D:\PPTest' is
> > > incorrectly formatted. Backups cannot be appended, but existing backup sets
> > > may still be usable. I have run dbcc checkdb checks on the source db and
> > > they seem ok. Any ideas why I am getting this error on the restore?