|
|
Posted by mike on 12/11/06 23:59
thanks for the information
Mike
"Erland Sommarskog" <esquel@sommarskog.se> wrote in message
news:Xns9896EFBA39B23Yazorman@127.0.0.1...
> mike (vettes_n_jets@yahoo.com) writes:
>> I agree with you michael....the excuse (reason) i was given is that they
>> did not trust sql64 at the time...just out of beta
>
> Now, wait! The only sql64 that in beta alone was Liberty, the 64-bit
> version of SQL 2000. If that version was an option for them, it means
> that your 64-bit box is an Itanium machine. As far as I know there is
> quite a performance penalty running 32-bit programs on Itanium.
>
> It's a different thing, if the machine is an x64 box. Particularly, if
> you are running SQL 2000, since there is no x64 version of SQL 2000.
> If you are running SQL 2005, the 64-bit version is still to prefer, I
> guess, but there is no direct penalty for running the 32-bit version
> on x64.
>
>> but the system waas moving along ok....and all of a sudden, come to a >
>> crawl running same as before this super slow down
>
> The cause could very well be that the query plans for some common queries
> have gone awry.
>
> I would run profiler and capture events that run more than, say, 100 ms.
> The events to include are RPC:Completed, SQL:BatchCompleted, SP:Completed,
> SP:StmtCompleted and SP:Recompile.
>
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
>
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|