database file locations: x64

Showing posts with label x64. Show all posts

Wednesday, March 21, 2012

New server with SQL Server 2005 standard x64 crashing

We have new 64-bit server and SQL Server 2005 where we moved databases and
applications from a 32-bit server and SQL Server 2000. Since we have moved
the databases and application to the new server the server crashes and
reboots at an irregular interval. This reboot seems to always be proceeded
by the memory working set for SQL Server being paged out and available memory
going up by a large amount. This usually occurs hours before the server
crashes. The available memory stays high until the server crashes.
OS: Server 2003 Standard edition x64 Edition
Version 5.2.3790 Service Pack 2 Build 3790
Hardware: HP ProLiant DL380 G5 with two Dual core cpu's 3000 MHz.
4 GB of memory
SQL Server Standard Edition (64-bit) Version: 9.00.3054.00
Using the performance monitory we can see the memory event that proceeds the
reboot and have ruled out some likely candidates like the Anti-virus and
backup software. The reboots occur anywhere from less the 24 hours apart to
4 days.
Does anyone know of any problems with SQL Server Standard x64 and memory
problems?
Any suggestions on how to identify if SQL Server is the problem or help
identifying some other service or driver as the cause of this problem?
--
MarkI have found it helpful to set the maximum memory setting in SQL Server to
less than the total available on the server. Based on the amount of memory
on the server this max amount would from 512 MB to 1024 MB less than the
maximum installed memory amount.
"masmith" wrote:
> We have new 64-bit server and SQL Server 2005 where we moved databases and
> applications from a 32-bit server and SQL Server 2000. Since we have moved
> the databases and application to the new server the server crashes and
> reboots at an irregular interval. This reboot seems to always be proceeded
> by the memory working set for SQL Server being paged out and available memory
> going up by a large amount. This usually occurs hours before the server
> crashes. The available memory stays high until the server crashes.
> OS: Server 2003 Standard edition x64 Edition
> Version 5.2.3790 Service Pack 2 Build 3790
> Hardware: HP ProLiant DL380 G5 with two Dual core cpu's 3000 MHz.
> 4 GB of memory
> SQL Server Standard Edition (64-bit) Version: 9.00.3054.00
> Using the performance monitory we can see the memory event that proceeds the
> reboot and have ruled out some likely candidates like the Anti-virus and
> backup software. The reboots occur anywhere from less the 24 hours apart to
> 4 days.
> Does anyone know of any problems with SQL Server Standard x64 and memory
> problems?
> Any suggestions on how to identify if SQL Server is the problem or help
> identifying some other service or driver as the cause of this problem?
> --
> Mark
>|||> Does anyone know of any problems with SQL Server Standard x64 and memory
> problems?
I dont have a link at hand, but I am pretty sure that SP2 for SQL Server
fixes this issue. We had the same issue from time to time, and we ended up
setting the min and max memory usage for the sql server 1 GB lower than the
total amount of memory. I searched google, and found a site saying, that the
SP2 would fix this issue.
If you haven't installed SP2, then you should take a look at the bugfixes
for that - and maybe you can permanent fix the problem with that.
/Sjang

new server to install, Win 2003 x64 will be used... which SQL Version?

Hi,
I have to install a new server and I am a little confused about working
combinations between 30bits, x64 and IA64...
My server use intel Xeon processors with EMT64.
So I want to install Windows 2003 x64 Ent.
but which version of SQL Server can I install?
the 64bits?
32bits + SP4 (Sql2k64sp4.exe)?
Also I have to install Reporting Services, Analysis Services & Sharepoint.
Does everything works on Win x64?
I'm using SQL Server 2000 enterprise edition.
thanks for your answer.
Jerome.You need the SQL Server 2000 (64-bit) edition.
http://www.microsoft.com/sql/64bit/default.mspx
--
--Brian
(Please reply to the newsgroups only.)
"Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
news:e%2313sduuFHA.3764@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have to install a new server and I am a little confused about working
> combinations between 30bits, x64 and IA64...
> My server use intel Xeon processors with EMT64.
> So I want to install Windows 2003 x64 Ent.
> but which version of SQL Server can I install?
> the 64bits?
> 32bits + SP4 (Sql2k64sp4.exe)?
> Also I have to install Reporting Services, Analysis Services & Sharepoint.
> Does everything works on Win x64?
> I'm using SQL Server 2000 enterprise edition.
> thanks for your answer.
> Jerome.
>|||what you really need; you need to wait for sql 2005 and it'll be a LOT
better|||unfortunatly its an hardware migration process.
we change an old server to a new one
so we can't deploy 2005.
but I have to insure that the 64bits edition (of SQL, RS, AS) works
correctly on Win 2003 x64.
if there is any issue or compatibility problem, I'll use the 32bit edition.
<dbahooker@.hotmail.com> wrote in message
news:1126900439.484602.107740@.g44g2000cwa.googlegroups.com...
> what you really need; you need to wait for sql 2005 and it'll be a LOT
> better
>|||Hi
No, 32 Bit plus SP4.
SQL Server 2000 64 Bit is complied for the Intel Itanium Processor and will
not run on Xeons.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Brian Lawton" <brian.k.lawton@.redtailcreek.com> wrote in message
news:%23QD6nsuuFHA.1472@.TK2MSFTNGP15.phx.gbl...
> You need the SQL Server 2000 (64-bit) edition.
> http://www.microsoft.com/sql/64bit/default.mspx
> --
> --Brian
> (Please reply to the newsgroups only.)
>
> "Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
> news:e%2313sduuFHA.3764@.TK2MSFTNGP09.phx.gbl...
>> Hi,
>> I have to install a new server and I am a little confused about working
>> combinations between 30bits, x64 and IA64...
>> My server use intel Xeon processors with EMT64.
>> So I want to install Windows 2003 x64 Ent.
>> but which version of SQL Server can I install?
>> the 64bits?
>> 32bits + SP4 (Sql2k64sp4.exe)?
>> Also I have to install Reporting Services, Analysis Services &
>> Sharepoint.
>> Does everything works on Win x64?
>> I'm using SQL Server 2000 enterprise edition.
>> thanks for your answer.
>> Jerome.
>>
>|||If you are going to install the 64-bit version of the Win2K3 make sure:
1) you install SP1 of Win2K3 x64 -- and
2) you use SP4
Both are required to run AS2K on x64 hardware with a 64-bit OS.
--
Dave Wickert [MSFT]
dwickert@.online.microsoft.com
Program Manager
BI Systems Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
news:ONOy27vuFHA.2072@.TK2MSFTNGP14.phx.gbl...
> unfortunatly its an hardware migration process.
> we change an old server to a new one
> so we can't deploy 2005.
> but I have to insure that the 64bits edition (of SQL, RS, AS) works
> correctly on Win 2003 x64.
> if there is any issue or compatibility problem, I'll use the 32bit
> edition.
>
> <dbahooker@.hotmail.com> wrote in message
> news:1126900439.484602.107740@.g44g2000cwa.googlegroups.com...
>> what you really need; you need to wait for sql 2005 and it'll be a LOT
>> better
>|||Thankls.
I have all of this on my CD Roms...
so finally, there is no issue in mind(?)
"Dave Wickert [MSFT]" <dwickert@.online.microsoft.com> wrote in message
news:%23ultf2XvFHA.4032@.TK2MSFTNGP15.phx.gbl...
> If you are going to install the 64-bit version of the Win2K3 make sure:
> 1) you install SP1 of Win2K3 x64 -- and
> 2) you use SP4
> Both are required to run AS2K on x64 hardware with a 64-bit OS.
> --
> Dave Wickert [MSFT]
> dwickert@.online.microsoft.com
> Program Manager
> BI Systems Team
> SQL BI Product Unit (Analysis Services)
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
> news:ONOy27vuFHA.2072@.TK2MSFTNGP14.phx.gbl...
>> unfortunatly its an hardware migration process.
>> we change an old server to a new one
>> so we can't deploy 2005.
>> but I have to insure that the 64bits edition (of SQL, RS, AS) works
>> correctly on Win 2003 x64.
>> if there is any issue or compatibility problem, I'll use the 32bit
>> edition.
>>
>> <dbahooker@.hotmail.com> wrote in message
>> news:1126900439.484602.107740@.g44g2000cwa.googlegroups.com...
>> what you really need; you need to wait for sql 2005 and it'll be a LOT
>> better
>>
>|||I will be deploying this same setup... Windows 2003 Standard x64
Edition running SQL Server 2000 Enterprise Edition SP4. The server I'm
running on has 8GB of RAM. Does anyone know how much RAM SQL Server
will use? My understanding is that this is not an AWE situtation
because the OS can natively address all 8GB of RAM.
Any advice on maximizing this setup would be greatly appreciated.
Thanks.
--
george sarlas
gsarlas@.yahoo.com|||> My understanding is that this is not an AWE situtation
> because the OS can natively address all 8GB of RAM.
You are right, SQL Server can access up to 512Gb of RAM, which is the
maximum currently supported by Win2K3 Server.
--
Regards
Darren Gosbell [MCSD]
<dgosbell_at_yahoo_dot_com>
Blog: http://www.geekswithblogs.net/darrengosbell|||I've deployed the 1st of my 2 new 64-bit servers. I did have to enable
AWE in SQL Server. But to support more than 4GB of RAM, I needed to
install SQL 2000 SP4 and the SP4 AWE Hotfix
(http://support.microsoft.com/default.aspx?kbid=899761).
-george|||If you have 64bit SQL 2k you do not need to enable AWE. The knowledge
base article you quote only applies to 32bit SQL 2k. 64bit SQL 2k can
address the maximum amount of memory that Win2k3 can support (which is
512Gb) without turning on any special settings.
--
Regards
Darren Gosbell [MCSD]
<dgosbell_at_yahoo_dot_com>
Blog: http://www.geekswithblogs.net/darrengosbell
In article <1130256929.245741.68610@.g44g2000cwa.googlegroups.com>,
gsarlas@.yahoo.com says...
> I've deployed the 1st of my 2 new 64-bit servers. I did have to enable
> AWE in SQL Server. But to support more than 4GB of RAM, I needed to
> install SQL 2000 SP4 and the SP4 AWE Hotfix
> (http://support.microsoft.com/default.aspx?kbid=899761).
> -george
>|||Just for clarification...
Unfortunately, SQL Server 2000 64-bit Edition does not work with x64
processors. It only works with the Itanium processor. I am running
32-bit SQL Server 2000 on 64-bit Windows 2003, thus I had to enable
AWE.
-george
Darren Gosbell wrote:
> If you have 64bit SQL 2k you do not need to enable AWE. The knowledge
> base article you quote only applies to 32bit SQL 2k. 64bit SQL 2k can
> address the maximum amount of memory that Win2k3 can support (which is
> 512Gb) without turning on any special settings.
> --
> Regards
> Darren Gosbell [MCSD]
> <dgosbell_at_yahoo_dot_com>
> Blog: http://www.geekswithblogs.net/darrengosbell
> In article <1130256929.245741.68610@.g44g2000cwa.googlegroups.com>,
> gsarlas@.yahoo.com says...
> > I've deployed the 1st of my 2 new 64-bit servers. I did have to enable
> > AWE in SQL Server. But to support more than 4GB of RAM, I needed to
> > install SQL 2000 SP4 and the SP4 AWE Hotfix
> > (http://support.microsoft.com/default.aspx?kbid=899761).
> >
> > -george
> >
> >

Wednesday, March 21, 2012

New server with SQL Server 2005 standard x64 crashing

new server to install, Win 2003 x64 will be used... which SQL Version?

new server to install, Win 2003 x64 will be used... which SQL Version?

new server to install, Win 2003 x64 will be used... which SQL Version?

new server to install, Win 2003 x64 will be used... which SQL Version?

database file locations

Blog Archive

About Me