database file locations: intel

Showing posts with label intel. Show all posts

Wednesday, March 21, 2012

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
> >
> >

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

Friday, March 9, 2012

New Intel PIV 2.8E 1M cache US$169 only

Place your order now, call: +86 13708077010 Chau Li Mawrote:

> Place your order now, call: +86 13708077010 Chau Li Ma
>

Wednesday, March 7, 2012

New installation - Catalog does not get popuated

I am tearing my hair out here!
I have set up a full text catlog on an SQL 2000 Server ( Microsoft SQL
Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05 ), and everything
seemed to go fine until I tried to populate it. It seems to get stuck in
populate mode, and the only errors that I can see are in the event log as
below.
I have looked at various postings on the subject, and the only one that I
can see is relevant is the one about SQL server running under a different
account to the LocalSystem, which it was. I corrected this via Enterprise
manager, re-started SQL Server, then re-started Microsoft Search/Full-text
Search, but still it does not populate!
The event log errors are:
One or more warnings or errors for Gatherer project <SQLServer
SQL0001800005> were logged to file <C:\Program Files\Microsoft SQL
Server\MSSQL\FTData\SQLServer\GatherLogs\SQL000180 0005.1.gthr>. If you are
interested in these messages, please, look at the file using the gatherer log
query object (gthrlog.vbs, log viewer web page).
Followed by:
The crawl seed <MSSQL75://SQLServer/64d0200a> in project <SQLServer
SQL0001800005> cannot be accessed. Error: 800700e9 - No process is on the
other end of the pipe. .
Any ideas?
Cheers, Mike.
SQL FTS uses named pipes to communicate with MSSearch.
The error message you are getting is most often related to security, such as
changing the SQL Server service account through control panel rather than
Enterprise Manager.
Can you confirm, that 1) a stopping and starting of MSSearch, SQL Server,
and even a reboot does not solve this problem. I can be resource related. 2)
secondly verify that the BuiltIn Administrators group is in your security
folder and is a system administrator.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Mike Owen" <MikeOwen@.discussions.microsoft.com> wrote in message
news:F1FF6F58-C7D3-4DC8-913B-9EB244CE6B5F@.microsoft.com...
> I am tearing my hair out here!
> I have set up a full text catlog on an SQL 2000 Server ( Microsoft SQL
> Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05 ), and
everything
> seemed to go fine until I tried to populate it. It seems to get stuck in
> populate mode, and the only errors that I can see are in the event log as
> below.
> I have looked at various postings on the subject, and the only one that I
> can see is relevant is the one about SQL server running under a different
> account to the LocalSystem, which it was. I corrected this via Enterprise
> manager, re-started SQL Server, then re-started Microsoft Search/Full-text
> Search, but still it does not populate!
> The event log errors are:
> One or more warnings or errors for Gatherer project <SQLServer
> SQL0001800005> were logged to file <C:\Program Files\Microsoft SQL
> Server\MSSQL\FTData\SQLServer\GatherLogs\SQL000180 0005.1.gthr>. If you are
> interested in these messages, please, look at the file using the gatherer
log
> query object (gthrlog.vbs, log viewer web page).
> Followed by:
> The crawl seed <MSSQL75://SQLServer/64d0200a> in project <SQLServer
> SQL0001800005> cannot be accessed. Error: 800700e9 - No process is on the
> other end of the pipe. .
> Any ideas?
>
> Cheers, Mike.
|||Mike,
Yes, I have an idea and thank you for providing the version (@.@.select) and
eventlog error as they are both very helpful info in troubleshooting SQL FTS
issues!
The primary error is "800700e9 - No process is on the other end of the
pipe.". This error is often caused by removing or altering the SQL Server
login BUILTIN\Administrators and it most likely is the source of this
problem for you. This most likely is the source of the failure for FT
Populations as the MSSearch service needs this login to log into SQL Server
and you can either add back this login with the original permissions
(default master db, sysadmin privileges or see KB article:
263712 (Q263712) INF: How to Impede Windows NT Administrators from
Administering a Clustered SQL Server at:
http://support.microsoft.com/default...B;EN-US;263712
If you cannot add back the SQL Server login BUILTIN\Administrators login,
you can use the following SQL code as a substitute:
exec sp_grantlogin N'NT Authority\System'
exec sp_defaultdb N'NT Authority\System', N'master'
exec sp_defaultlanguage N'NT Authority\System','us_english'
exec sp_addsrvrolemember N'NT Authority\System', sysadmin
Regards,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Mike Owen" <MikeOwen@.discussions.microsoft.com> wrote in message
news:F1FF6F58-C7D3-4DC8-913B-9EB244CE6B5F@.microsoft.com...
> I am tearing my hair out here!
> I have set up a full text catlog on an SQL 2000 Server ( Microsoft SQL
> Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05 ), and
everything
> seemed to go fine until I tried to populate it. It seems to get stuck in
> populate mode, and the only errors that I can see are in the event log as
> below.
> I have looked at various postings on the subject, and the only one that I
> can see is relevant is the one about SQL server running under a different
> account to the LocalSystem, which it was. I corrected this via Enterprise
> manager, re-started SQL Server, then re-started Microsoft Search/Full-text
> Search, but still it does not populate!
> The event log errors are:
> One or more warnings or errors for Gatherer project <SQLServer
> SQL0001800005> were logged to file <C:\Program Files\Microsoft SQL
> Server\MSSQL\FTData\SQLServer\GatherLogs\SQL000180 0005.1.gthr>. If you are
> interested in these messages, please, look at the file using the gatherer
log
> query object (gthrlog.vbs, log viewer web page).
> Followed by:
> The crawl seed <MSSQL75://SQLServer/64d0200a> in project <SQLServer
> SQL0001800005> cannot be accessed. Error: 800700e9 - No process is on the
> other end of the pipe. .
> Any ideas?
>
> Cheers, Mike.
|||Thanks Hilary, I had previously checked to see what permissions the
BUILTIN\Administrators user(s) had on all the DB's, which was db_owner, but I
didn't check it's 'Server Roles' - It had no server roles, and as soon as I
gave it System Administrators Role eveything started working!
Thanks for your help, Mike.
"Hilary Cotter" wrote:

> SQL FTS uses named pipes to communicate with MSSearch.
> The error message you are getting is most often related to security, such as
> changing the SQL Server service account through control panel rather than
> Enterprise Manager.
> Can you confirm, that 1) a stopping and starting of MSSearch, SQL Server,
> and even a reboot does not solve this problem. I can be resource related. 2)
> secondly verify that the BuiltIn Administrators group is in your security
> folder and is a system administrator.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Mike Owen" <MikeOwen@.discussions.microsoft.com> wrote in message
> news:F1FF6F58-C7D3-4DC8-913B-9EB244CE6B5F@.microsoft.com...
> everything
> log
>
>
|||Thanks for replying John.
I worked through Hilary's answer first (as it was posted first), which I
think was similar to yours, and added BUILTIN\Administrators to the 'System
Administrators' Role, and it all started working.
Cheers, Mike.
"John Kane" wrote:

> Mike,
> Yes, I have an idea and thank you for providing the version (@.@.select) and
> eventlog error as they are both very helpful info in troubleshooting SQL FTS
> issues!
> The primary error is "800700e9 - No process is on the other end of the
> pipe.". This error is often caused by removing or altering the SQL Server
> login BUILTIN\Administrators and it most likely is the source of this
> problem for you. This most likely is the source of the failure for FT
> Populations as the MSSearch service needs this login to log into SQL Server
> and you can either add back this login with the original permissions
> (default master db, sysadmin privileges or see KB article:
> 263712 (Q263712) INF: How to Impede Windows NT Administrators from
> Administering a Clustered SQL Server at:
> http://support.microsoft.com/default...B;EN-US;263712
> If you cannot add back the SQL Server login BUILTIN\Administrators login,
> you can use the following SQL code as a substitute:
> exec sp_grantlogin N'NT Authority\System'
> exec sp_defaultdb N'NT Authority\System', N'master'
> exec sp_defaultlanguage N'NT Authority\System','us_english'
> exec sp_addsrvrolemember N'NT Authority\System', sysadmin
> Regards,
> John
> --
> SQL Full Text Search Blog
> http://spaces.msn.com/members/jtkane/
>
> "Mike Owen" <MikeOwen@.discussions.microsoft.com> wrote in message
> news:F1FF6F58-C7D3-4DC8-913B-9EB244CE6B5F@.microsoft.com...
> everything
> log
>
>

Wednesday, March 21, 2012

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?

Friday, March 9, 2012

New Intel PIV 2.8E 1M cache US$169 only

Wednesday, March 7, 2012

New installation - Catalog does not get popuated

database file locations

Blog Archive

About Me