Posted by mike on 12/11/06 15:17

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

so im trying to figure out why the system has come to a crawl...i know i
have to re-write alot of the stored procs
but the system waas moving along ok....and all of a sudden, come to a crawl
running same as before this super slow down
Nas Drives working ok, Network speaking ok
public net is 10/100, private network 10/100/1000
hard ware is 4 cpu...sql has 3, 4g mem (more mem required) 2.8 cpu's

so any information is welcome...
thanks
mike





"Michael Austin" <maustin@firstdbasource.com> wrote in message
news:0UXeh.4340$Gr2.1021@newssvr21.news.prodigy.net...
> mike wrote:
>
>> I have found that orig tested 64 bit on our 64bit windows 2003
>> server...about 1 year ago...and company decided to use sql 32 bit on the
>> 64bit os
>>
>> my question and any information is very welcome
>>
>> is there any things in need to know about awe with
>> memory above 4g ...whilst using 32 bit sql on a 64bit os
>> i want to increase the memory on the server but
>> i really don't know what im up against since this is
>> mixed system 32 bit sql and 64 bit os
>>
>> thanks
>> mike
>>
>>
>>
>
> what was the excuse used to persuade them to use 32bit vs 64bit? (note I
> said excuse not reason) If you are going to invest in a 64bit architecture
> and 64bit OS - it is beyond insanity to install a 32bit database.
>
> --
> Michael Austin.
> Database Consultant

• Next in forum: Re: PRINT debug messages and CURSOR in stored procedure confuses DTS; "Invalid Pointer"
• Prev in forum: asdb - what is it? Shold I back it up?
• Thread view: Re: memory 64bit windows , 32 bit Sql

[Reply to this message]