Showing posts with label statistics. Show all posts
Showing posts with label statistics. Show all posts

Sunday, March 25, 2012

32bit to 64bit Server performance is very poor

Hi
You would really have to post something more specific, but...
Have you updated the statistics and indexes?
Make sure that your configuration options have not changed (sp_configure)
e.g. check that you are using the right amount of memory, CPU affinity etc..
Check database options (sp_dboptions) to make sure that setting are
consistent (e.g Autoshrink is not on!)
Check that you have not introduced an IO bottleneck (e.g logs and data on
same disc or disc sector size has not been set correctly).
Run SQL profiler to identify what is taking a prolong time and investigate
specific queries/procedures.
Use Performance Monitor to check for other issues.
HTH
John
"Jaison Jose" wrote:

> Dear Team,
> After migrating to sql server 2000 32 bit to sql server 2000 64 bit, we ar
e
> facing performance related issues....Could any one help me plz?
> Previous OS was win2003 EE(X86),Now we are using win2003 EE with SP1,Itani
um
> 2(IA64).
> Regards,
> JaisonDear Team,
After migrating to sql server 2000 32 bit to sql server 2000 64 bit, we are
facing performance related issues....Could any one help me plz?
Previous OS was win2003 EE(X86),Now we are using win2003 EE with SP1,Itanium
2(IA64).
Regards,
Jaison|||Hi
You would really have to post something more specific, but...
Have you updated the statistics and indexes?
Make sure that your configuration options have not changed (sp_configure)
e.g. check that you are using the right amount of memory, CPU affinity etc..
Check database options (sp_dboptions) to make sure that setting are
consistent (e.g Autoshrink is not on!)
Check that you have not introduced an IO bottleneck (e.g logs and data on
same disc or disc sector size has not been set correctly).
Run SQL profiler to identify what is taking a prolong time and investigate
specific queries/procedures.
Use Performance Monitor to check for other issues.
HTH
John
"Jaison Jose" wrote:

> Dear Team,
> After migrating to sql server 2000 32 bit to sql server 2000 64 bit, we ar
e
> facing performance related issues....Could any one help me plz?
> Previous OS was win2003 EE(X86),Now we are using win2003 EE with SP1,Itani
um
> 2(IA64).
> Regards,
> Jaison|||Hi John,
Statistics are updated. All the options are set as it was there in the
previous environment. The data and log file are on the same disc. But john,
this all settings are quite fine with Xeon Processors, the cpu utilization
was only ranging in between 10-15%. Application was working very well.But
When it comes to itanium , suddenly the environment has changed. The cpu
starts shooting upto 90%. I just want to know one thing , If i want to move
a
32 bit database to a 64 bit environment, what and all the wright steps that
i
need to take before proceeding with the migration?....So that i can come to
know where i went wrong....
Regards,
Jaison Jose
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> You would really have to post something more specific, but...
> Have you updated the statistics and indexes?
> Make sure that your configuration options have not changed (sp_configure)
> e.g. check that you are using the right amount of memory, CPU affinity etc
.
> Check database options (sp_dboptions) to make sure that setting are
> consistent (e.g Autoshrink is not on!)
> Check that you have not introduced an IO bottleneck (e.g logs and data on
> same disc or disc sector size has not been set correctly).
> Run SQL profiler to identify what is taking a prolong time and investigate
> specific queries/procedures.
> Use Performance Monitor to check for other issues.
> HTH
> John
> "Jaison Jose" wrote:
>|||Hi John,
Statistics are updated. All the options are set as it was there in the
previous environment. The data and log file are on the same disc. But john,
this all settings are quite fine with Xeon Processors, the cpu utilization
was only ranging in between 10-15%. Application was working very well.But
When it comes to itanium , suddenly the environment has changed. The cpu
starts shooting upto 90%. I just want to know one thing , If i want to move
a
32 bit database to a 64 bit environment, what and all the wright steps that
i
need to take before proceeding with the migration?....So that i can come to
know where i went wrong....
Regards,
Jaison Jose
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> You would really have to post something more specific, but...
> Have you updated the statistics and indexes?
> Make sure that your configuration options have not changed (sp_configure)
> e.g. check that you are using the right amount of memory, CPU affinity etc
.
> Check database options (sp_dboptions) to make sure that setting are
> consistent (e.g Autoshrink is not on!)
> Check that you have not introduced an IO bottleneck (e.g logs and data on
> same disc or disc sector size has not been set correctly).
> Run SQL profiler to identify what is taking a prolong time and investigate
> specific queries/procedures.
> Use Performance Monitor to check for other issues.
> HTH
> John
> "Jaison Jose" wrote:
>|||Hi Jaison
When you have
http://www.microsoft.com/sql/soluti...ingto64bit.mspx it sounds
easy, but as this is a migration and not a in-situ upgrade you need to
consider all the factors that a migration entails.
You may want to read
http://www.microsoft.com/technet/pr...on.ms
px which covers alot of the things you should check regardless of version.
You may also want to do some monitoring with performance monitor such as
http://www.sql-server-performance.c...nce_article.asp
Also if this is a new system then running SQLIOStress may be a good idea.
I assume that you have checked that the hardware is supported by the version
of SQL Server you are using
http://msdn.microsoft.com/library/d...>
g64_2ctv.asp and everything is service packed?
John
"Jaison Jose" wrote:
[vbcol=seagreen]
> Hi John,
> Statistics are updated. All the options are set as it was there in the
> previous environment. The data and log file are on the same disc. But john
,
> this all settings are quite fine with Xeon Processors, the cpu utilization
> was only ranging in between 10-15%. Application was working very well.But
> When it comes to itanium , suddenly the environment has changed. The cpu
> starts shooting upto 90%. I just want to know one thing , If i want to mov
e a
> 32 bit database to a 64 bit environment, what and all the wright steps tha
t i
> need to take before proceeding with the migration?....So that i can come
to
> know where i went wrong....
> Regards,
> Jaison Jose
>
> "John Bell" wrote:
>|||Hai John,
I had created a fresh database in the 64 bit new server. Then
I had generated a complete script(database->alltask->generate script-> ) from
the 32 bit sql server and made it run on 64 bit. And then done a DTS to move
the data to the newly created database. The reason why i had gone for this
way is nothing but while trying for an attach i was facing some error(Sorry,
i am not remembering exactly the error..).
Does this cause any issue?
If something had gone wrong with this, Will it be possible me to configure
it proper..?
"Jaison Jose" wrote:

> Dear Team,
> After migrating to sql server 2000 32 bit to sql server 2000 64 bit, we ar
e
> facing performance related issues....Could any one help me plz?
> Previous OS was win2003 EE(X86),Now we are using win2003 EE with SP1,Itani
um
> 2(IA64).
> Regards,
> Jaison|||Hi Jaison
Check that the indexes were scripted properly. If data was pumped into the
tables after creating the indexes you would need to rebuild the indexes. If
you have auto create stats on for you database then you will have lost these
.
Backup/restore should have worked fine when transferring the database as
well as detach/attach which should be significantly quicker than your method
so you may want to try it again.
John
"Jaison Jose" wrote:
[vbcol=seagreen]
> Hai John,
> I had created a fresh database in the 64 bit new server. Then
> I had generated a complete script(database->alltask->generate script-> ) fr
om
> the 32 bit sql server and made it run on 64 bit. And then done a DTS to mo
ve
> the data to the newly created database. The reason why i had gone for this
> way is nothing but while trying for an attach i was facing some error(Sorr
y,
> i am not remembering exactly the error..).
> Does this cause any issue?
> If something had gone wrong with this, Will it be possible me to configure
> it proper..?
>
> "Jaison Jose" wrote:
>|||Hi John,
USE Database_Name
GO
EXEC sp_MSforeachtable @.command1="print '?' DBCC DBREINDEX ('?', ' ', 80)"
GO
Hope this will do. Appreciate ur comments as well.
I had already done an index defragmentation by using DBCC INDEXDEFRAG
statement , but no visible effects. In this case is there any difference
between
DBCC INDEXDEFRAG and DBCC DBREINDEX ?
Regards,
Jaison
"John Bell" wrote:
[vbcol=seagreen]
> Hi Jaison
> Check that the indexes were scripted properly. If data was pumped into the
> tables after creating the indexes you would need to rebuild the indexes. I
f
> you have auto create stats on for you database then you will have lost the
se.
> Backup/restore should have worked fine when transferring the database as
> well as detach/attach which should be significantly quicker than your meth
od
> so you may want to try it again.
> John
> "Jaison Jose" wrote:
>|||Hi Jaison
When you have
http://www.microsoft.com/sql/soluti...ingto64bit.mspx it sounds
easy, but as this is a migration and not a in-situ upgrade you need to
consider all the factors that a migration entails.
You may want to read
http://www.microsoft.com/technet/pr...on.ms
px which covers alot of the things you should check regardless of version.
You may also want to do some monitoring with performance monitor such as
http://www.sql-server-performance.c...nce_article.asp
Also if this is a new system then running SQLIOStress may be a good idea.
I assume that you have checked that the hardware is supported by the version
of SQL Server you are using
http://msdn.microsoft.com/library/d...>
g64_2ctv.asp and everything is service packed?
John
"Jaison Jose" wrote:
[vbcol=seagreen]
> Hi John,
> Statistics are updated. All the options are set as it was there in the
> previous environment. The data and log file are on the same disc. But john
,
> this all settings are quite fine with Xeon Processors, the cpu utilization
> was only ranging in between 10-15%. Application was working very well.But
> When it comes to itanium , suddenly the environment has changed. The cpu
> starts shooting upto 90%. I just want to know one thing , If i want to mov
e a
> 32 bit database to a 64 bit environment, what and all the wright steps tha
t i
> need to take before proceeding with the migration?....So that i can come
to
> know where i went wrong....
> Regards,
> Jaison Jose
>
> "John Bell" wrote:
>

Tuesday, March 6, 2012

2005 Update Statistics Task fails

Hi,
Can anyone, given the history below, tell me why this task fails? Or could
you tell me how to figure out why the task fails?
Thanks,
Jim
Windows Server 2003 SP2
Microsoft SQL Server 2005 - 9.00.3054.00 (X64) Mar 23 2007 18:41:50
Copyright (c) 1988-2005 Microsoft Corporation Standard Edition (64-bit) on
Windows NT 5.2 (Build 3790: Service Pack 2)
---
Date 9/10/2007 9:58:00 AM
Log Job History (User Maintenance.Update Statistics)
Step ID 1
Server GENOME-GENDB
Job Name User Maintenance.Update Statistics
Step Name Update Statistics
Duration 00:03:00
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Message
Executed as user: <our_domain>\<our_sql_server_account>. ...00.3042.00 for
64-bit Copyright (C) Microsoft Corp 1984-2005.
All rights reserved.
Started: 9:58:00 AM
Progress: 2007-09-10 09:58:00.59
Source: {5D469B6D-98A4-4907-92D7-904C931892B5}
Executing query "DECLARE @.Guid UNIQUEIDENTIFIER EXECUTE msdb..sp".:
100% complete
End Progress
Progress: 2007-09-10 10:00:10.27
Source: Update Statistics Task
Executing query "use [blast_xml] ".: 12% complete
End Progress
Progress: 2007-09-10 10:00:10.33
Source: Update Statistics Task
Executing query "UPDATE STATISTICS [dbo].[tBlastOutput] WITH SAMP".: 25%
complete
End Progress
Progress: 2007-09-10 10:00:10.33
Source: Update Statistics Task
Executing query "use [blast_xml] ".: 37% complete
End Progress
Progress: 2007-09-10 10:00:10.44
Source: Update Statistics Task
Executing query "UPDATE STATISTICS [dbo].[tBlastRun] WITH SAMPLE ".: 50%
complete
End Progress
Progres... The package execution fa... The step failed.I would create a text file for the log for more details, instead of just
relying on the job history.
You can also execute the SSIS package while in the designer window and watch
which step fails in the debug mode.
"Jim" <noreply@.noreply.com> wrote in message
news:eEJ35X88HHA.4752@.TK2MSFTNGP04.phx.gbl...
> Hi,
> Can anyone, given the history below, tell me why this task fails? Or
> could you tell me how to figure out why the task fails?
> Thanks,
> Jim
> Windows Server 2003 SP2
> Microsoft SQL Server 2005 - 9.00.3054.00 (X64) Mar 23 2007 18:41:50
> Copyright (c) 1988-2005 Microsoft Corporation Standard Edition (64-bit)
> on Windows NT 5.2 (Build 3790: Service Pack 2)
> ---
> Date 9/10/2007 9:58:00 AM
> Log Job History (User Maintenance.Update Statistics)
> Step ID 1
> Server GENOME-GENDB
> Job Name User Maintenance.Update Statistics
> Step Name Update Statistics
> Duration 00:03:00
> Sql Severity 0
> Sql Message ID 0
> Operator Emailed
> Operator Net sent
> Operator Paged
> Retries Attempted 0
> Message
> Executed as user: <our_domain>\<our_sql_server_account>. ...00.3042.00 for
> 64-bit Copyright (C) Microsoft Corp 1984-2005.
> All rights reserved.
> Started: 9:58:00 AM
> Progress: 2007-09-10 09:58:00.59
> Source: {5D469B6D-98A4-4907-92D7-904C931892B5}
> Executing query "DECLARE @.Guid UNIQUEIDENTIFIER EXECUTE msdb..sp".:
> 100% complete
> End Progress
> Progress: 2007-09-10 10:00:10.27
> Source: Update Statistics Task
> Executing query "use [blast_xml] ".: 12% complete
> End Progress
> Progress: 2007-09-10 10:00:10.33
> Source: Update Statistics Task
> Executing query "UPDATE STATISTICS [dbo].[tBlastOutput] WITH SAMP".: 25%
> complete
> End Progress
> Progress: 2007-09-10 10:00:10.33
> Source: Update Statistics Task
> Executing query "use [blast_xml] ".: 37% complete
> End Progress
> Progress: 2007-09-10 10:00:10.44
> Source: Update Statistics Task
> Executing query "UPDATE STATISTICS [dbo].[tBlastRun] WITH SAMPLE ".: 50%
> complete
> End Progress
> Progres... The package execution fa... The step failed.
>|||Thank you, YPD. I will keep this in mind when I return to troubleshooting
that situation.
"YPD" <y.ding@.neu.edu> wrote in message
news:286E5C59-EE3E-4263-96C1-D51E7461915A@.microsoft.com...
>I would create a text file for the log for more details, instead of just
>relying on the job history.
> You can also execute the SSIS package while in the designer window and
> watch which step fails in the debug mode.
>
> "Jim" <noreply@.noreply.com> wrote in message
> news:eEJ35X88HHA.4752@.TK2MSFTNGP04.phx.gbl...
>> Hi,
>> Can anyone, given the history below, tell me why this task fails? Or
>> could you tell me how to figure out why the task fails?
>> Thanks,
>> Jim
>> Windows Server 2003 SP2
>> Microsoft SQL Server 2005 - 9.00.3054.00 (X64) Mar 23 2007 18:41:50
>> Copyright (c) 1988-2005 Microsoft Corporation Standard Edition (64-bit)
>> on Windows NT 5.2 (Build 3790: Service Pack 2)
>> ---
>> Date 9/10/2007 9:58:00 AM
>> Log Job History (User Maintenance.Update Statistics)
>> Step ID 1
>> Server GENOME-GENDB
>> Job Name User Maintenance.Update Statistics
>> Step Name Update Statistics
>> Duration 00:03:00
>> Sql Severity 0
>> Sql Message ID 0
>> Operator Emailed
>> Operator Net sent
>> Operator Paged
>> Retries Attempted 0
>> Message
>> Executed as user: <our_domain>\<our_sql_server_account>. ...00.3042.00
>> for 64-bit Copyright (C) Microsoft Corp 1984-2005.
>> All rights reserved.
>> Started: 9:58:00 AM
>> Progress: 2007-09-10 09:58:00.59
>> Source: {5D469B6D-98A4-4907-92D7-904C931892B5}
>> Executing query "DECLARE @.Guid UNIQUEIDENTIFIER EXECUTE msdb..sp".:
>> 100% complete
>> End Progress
>> Progress: 2007-09-10 10:00:10.27
>> Source: Update Statistics Task
>> Executing query "use [blast_xml] ".: 12% complete
>> End Progress
>> Progress: 2007-09-10 10:00:10.33
>> Source: Update Statistics Task
>> Executing query "UPDATE STATISTICS [dbo].[tBlastOutput] WITH SAMP".:
>> 25% complete
>> End Progress
>> Progress: 2007-09-10 10:00:10.33
>> Source: Update Statistics Task
>> Executing query "use [blast_xml] ".: 37% complete
>> End Progress
>> Progress: 2007-09-10 10:00:10.44
>> Source: Update Statistics Task
>> Executing query "UPDATE STATISTICS [dbo].[tBlastRun] WITH SAMPLE ".:
>> 50% complete
>> End Progress
>> Progres... The package execution fa... The step failed.
>>
>