memory 64bit windows , 32 bit Sql

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • mike

    memory 64bit windows , 32 bit Sql

    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



  • Michael Austin

    #2
    Re: memory 64bit windows , 32 bit Sql

    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

    Comment

    • mike

      #3
      Re: memory 64bit windows , 32 bit Sql

      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@firstd basource.comwro te in message
      news:0UXeh.4340 $Gr2.1021@newss vr21.news.prodi gy.net...
      mike wrote:
      >
      >I have found that orig tested 64 bit on our 64bit windows 2003
      >server...abo ut 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

      Comment

      • Erland Sommarskog

        #4
        Re: memory 64bit windows , 32 bit Sql

        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:BatchComple ted, SP:Completed,
        SP:StmtComplete d and SP:Recompile.


        --
        Erland Sommarskog, SQL Server MVP, esquel@sommarsk og.se

        Books Online for SQL Server 2005 at

        Books Online for SQL Server 2000 at

        Comment

        • mike

          #5
          Re: memory 64bit windows , 32 bit Sql

          thanks for the information

          Mike

          "Erland Sommarskog" <esquel@sommars kog.sewrote in message
          news:Xns9896EFB A39B23Yazorman@ 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:BatchComple ted, SP:Completed,
          SP:StmtComplete d and SP:Recompile.
          >
          >
          --
          Erland Sommarskog, SQL Server MVP, esquel@sommarsk og.se
          >
          Books Online for SQL Server 2005 at

          Books Online for SQL Server 2000 at
          http://www.microsoft.com/sql/prodinf...ons/books.mspx

          Comment

          Working...