3G ram for SQL server: installation

Showing posts with label installation. Show all posts

Monday, March 19, 2012

8GB memory installation

Situation:
OS: 2000 advanced server
SQL enterprise
We have just added an extra 6GB of memory to our database server which
brings the total to 8. The problem we are having is that the OS is only using
3Gb of memory.
We have run the SP that is recommended for AWE and entered the /3GB /PAE in
the boot.ini file and restarted the machine.
The server still refuses to use more than 3GB. Any ideas?Did you re-configure SQL, the AWE and fixed memory?
e.g.
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'min server memory', 6656 (make same as maximum)
RECONFIGURE
go
sp_configure 'max server memory', 6656 (leave at least 512 for the OS)
RECONFIGURE
Regards
Mike
"lramsdale" wrote:
> Situation:
> OS: 2000 advanced server
> SQL enterprise
> We have just added an extra 6GB of memory to our database server which
> brings the total to 8. The problem we are having is that the OS is only using
> 3Gb of memory.
> We have run the SP that is recommended for AWE and entered the /3GB /PAE in
> the boot.ini file and restarted the machine.
> The server still refuses to use more than 3GB. Any ideas?|||This is what we ran:
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
"Mike Epprecht (SQL MVP)" wrote:
> Did you re-configure SQL, the AWE and fixed memory?
> e.g.
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> sp_configure 'min server memory', 6656 (make same as maximum)
> RECONFIGURE
> go
> sp_configure 'max server memory', 6656 (leave at least 512 for the OS)
> RECONFIGURE
> Regards
> Mike
> "lramsdale" wrote:
> > Situation:
> >
> > OS: 2000 advanced server
> > SQL enterprise
> >
> > We have just added an extra 6GB of memory to our database server which
> > brings the total to 8. The problem we are having is that the OS is only using
> > 3Gb of memory.
> >
> > We have run the SP that is recommended for AWE and entered the /3GB /PAE in
> > the boot.ini file and restarted the machine.
> >
> > The server still refuses to use more than 3GB. Any ideas?|||Ok we finally got to the bottom of this problem - it seems that we needed to
give the SQL server service account permissions to the lock pages in memory
privelege, even though it was in the domain admin account. This was hard to
find, why is there so much conflicting documentation on this AWE setting?
"lramsdale" wrote:
> This is what we ran:
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> sp_configure 'max server memory', 6144
> RECONFIGURE
> GO
> "Mike Epprecht (SQL MVP)" wrote:
> > Did you re-configure SQL, the AWE and fixed memory?
> >
> > e.g.
> >
> > sp_configure 'show advanced options', 1
> > RECONFIGURE
> > GO
> > sp_configure 'awe enabled', 1
> > RECONFIGURE
> > GO
> > sp_configure 'min server memory', 6656 (make same as maximum)
> > RECONFIGURE
> > go
> > sp_configure 'max server memory', 6656 (leave at least 512 for the OS)
> > RECONFIGURE
> >
> > Regards
> > Mike
> >
> > "lramsdale" wrote:
> >
> > > Situation:
> > >
> > > OS: 2000 advanced server
> > > SQL enterprise
> > >
> > > We have just added an extra 6GB of memory to our database server which
> > > brings the total to 8. The problem we are having is that the OS is only using
> > > 3Gb of memory.
> > >
> > > We have run the SP that is recommended for AWE and entered the /3GB /PAE in
> > > the boot.ini file and restarted the machine.
> > >
> > > The server still refuses to use more than 3GB. Any ideas?

Tuesday, March 6, 2012

64-bit SQL Server 2005 Installation (Reporting Services)

Hi,

Trying to install 64-bit SQL Server 2005 RTM on Windows 2003 x64 Server. The Reporting services is not getting installed or the option is disabled. The server does have IIS installed, the .NET framework 2.0 is installed by SQL Server 2005 RTM itself. The server also has SQL Server 2000 (32bit).

Is the 32-bit SQL Server 2000 (32 bit) a problem ? But, it was working fine with the SQL Server 2005 CTP.

Can anyone help/suggest ?

Thanks in advance.remove other reporting services from your machine. and try again

64bit SQl

Hello,
how do I find out if my SQL iNstallation is a 64bit or 32bit installation.
The OS is windows server 2003 64bit.
--
taniHi
Open Error Log and at the top should be written Microsoft SQL Server 2005 -
9.00.3042.00 (X64) which means 64 bit
"tani" <tani@.discussions.microsoft.com> wrote in message
news:508C63C4-BE8A-487C-B130-FA9008A51F15@.microsoft.com...
> Hello,
> how do I find out if my SQL iNstallation is a 64bit or 32bit installation.
> The OS is windows server 2003 64bit.
> --
> tani|||sorry.. but where do I find the error log?
thanks
--
tani
"Uri Dimant" wrote:
> Hi
> Open Error Log and at the top should be written Microsoft SQL Server 2005 -
> 9.00.3042.00 (X64) which means 64 bit
> "tani" <tani@.discussions.microsoft.com> wrote in message
> news:508C63C4-BE8A-487C-B130-FA9008A51F15@.microsoft.com...
> > Hello,
> >
> > how do I find out if my SQL iNstallation is a 64bit or 32bit installation.
> > The OS is windows server 2003 64bit.
> > --
> > tani
>
>|||tani
Do you know the path of SQL Server installation?
By default, the error log is located at Program Files\Microsoft SQL
Server\MSSQL.n\MSSQL\LOG\ERRORLOG
"tani" <tani@.discussions.microsoft.com> wrote in message
news:E4D8091E-2BE7-4DBF-BC4F-E4FA72A32698@.microsoft.com...
> sorry.. but where do I find the error log?
> thanks
> --
> tani
>
> "Uri Dimant" wrote:
>> Hi
>> Open Error Log and at the top should be written Microsoft SQL Server
>> 2005 -
>> 9.00.3042.00 (X64) which means 64 bit
>> "tani" <tani@.discussions.microsoft.com> wrote in message
>> news:508C63C4-BE8A-487C-B130-FA9008A51F15@.microsoft.com...
>> > Hello,
>> >
>> > how do I find out if my SQL iNstallation is a 64bit or 32bit
>> > installation.
>> > The OS is windows server 2003 64bit.
>> > --
>> > tani
>>|||Sorry.. I was looking on the completely wrong place..
I found it now.. thanks a lot!
--
tani
"Uri Dimant" wrote:
> tani
> Do you know the path of SQL Server installation?
> By default, the error log is located at Program Files\Microsoft SQL
> Server\MSSQL.n\MSSQL\LOG\ERRORLOG
>
>
> "tani" <tani@.discussions.microsoft.com> wrote in message
> news:E4D8091E-2BE7-4DBF-BC4F-E4FA72A32698@.microsoft.com...
> > sorry.. but where do I find the error log?
> > thanks
> > --
> > tani
> >
> >
> > "Uri Dimant" wrote:
> >
> >> Hi
> >> Open Error Log and at the top should be written Microsoft SQL Server
> >> 2005 -
> >> 9.00.3042.00 (X64) which means 64 bit
> >>
> >> "tani" <tani@.discussions.microsoft.com> wrote in message
> >> news:508C63C4-BE8A-487C-B130-FA9008A51F15@.microsoft.com...
> >> > Hello,
> >> >
> >> > how do I find out if my SQL iNstallation is a 64bit or 32bit
> >> > installation.
> >> > The OS is windows server 2003 64bit.
> >> > --
> >> > tani
> >>
> >>
> >>
>
>|||TO add to Uri's response, you can get the same info using SELECT @.@.VERSION.
On my 64-but test machine, this returns:
Microsoft SQL Server 2005 - 9.00.3054.00 (X64)
--
Hope this helps.
Dan Guzman
SQL Server MVP
"tani" <tani@.discussions.microsoft.com> wrote in message
news:508C63C4-BE8A-487C-B130-FA9008A51F15@.microsoft.com...
> Hello,
> how do I find out if my SQL iNstallation is a 64bit or 32bit installation.
> The OS is windows server 2003 64bit.
> --
> tani|||Dan
I did not think about it, thanks :-)))
Uh, its time to go home..
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:A1EA8611-5672-4555-8C8F-AA6DCB6EB3C6@.microsoft.com...
> TO add to Uri's response, you can get the same info using SELECT
> @.@.VERSION. On my 64-but test machine, this returns:
> Microsoft SQL Server 2005 - 9.00.3054.00 (X64)
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "tani" <tani@.discussions.microsoft.com> wrote in message
> news:508C63C4-BE8A-487C-B130-FA9008A51F15@.microsoft.com...
>> Hello,
>> how do I find out if my SQL iNstallation is a 64bit or 32bit
>> installation.
>> The OS is windows server 2003 64bit.
>> --
>> tani
>

64-bit problem

Hi,
I have an issue with a 64-bit clustered installation that I've just
completed, obviously the management tools can run on the itaniums and
I've put them on a 32-bit server on the same LAN.
My problem concerns creating the full-text indexes that I used to have
on a database. In a nutshell the MMC keeps telling me that the
Full-Text Search service must be running in order to do it (and the
MMC icon does show itself as being RED) but when I click on the
properties for it I get the correct response back that it is really
active. Everything to do with Full-Text is greyed out.
I know that I could script it but ideally I'll like to know if there's
some sort of hack available to make this work properly instead.
Thanks in advance for your help,
Mike
Mike,
Can you post the full output from -- SELECT @.@.version -- from your 64-bit
server? I'm assuming you're using the SQL Server 2000 (64-bit) EE version,
but need to confirm this. Additionally, what account ("System
account"/LocalSystem or DOMAIN\account) are you using for the MSSQLServer
account?
I've some experience with 64-bit SQL Server as I did some benchmarking tests
with Unisys at their lab in L.A. and the MSSearch service was functional,
however I didn't have the time to do FTS testing as we were busy testing
64-bit vs. 32-bit performance comparisons.
Since this is a clustered environment, this issue most likely is related to
either what account you have MSSQLServer running under or perhaps an
installation of the FTS components problem.
Thanks,
John
"Mike" <mike.metcalf@.4projects.com> wrote in message
news:678e073d.0411170818.5ae2e5f3@.posting.google.c om...
> Hi,
> I have an issue with a 64-bit clustered installation that I've just
> completed, obviously the management tools can run on the itaniums and
> I've put them on a 32-bit server on the same LAN.
> My problem concerns creating the full-text indexes that I used to have
> on a database. In a nutshell the MMC keeps telling me that the
> Full-Text Search service must be running in order to do it (and the
> MMC icon does show itself as being RED) but when I click on the
> properties for it I get the correct response back that it is really
> active. Everything to do with Full-Text is greyed out.
> I know that I could script it but ideally I'll like to know if there's
> some sort of hack available to make this work properly instead.
> Thanks in advance for your help,
> Mike
|||Hi John,
it turns out that it was just a blip in the installation and wasnt that
much of a one at that.
It's all working properly now and I for one am really impressed with the
performance increase we're getting across the board.
Thanks for helping,
Mike
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||You're welcome, Mike,
Sometimes, all it takes to solve a problem, is to either wait long enough
(for it to solve itself) or reboot! :-)
John
"Mike Metcalf" <mike.metcalf@.4projects.com> wrote in message
news:OBPjpoizEHA.1292@.TK2MSFTNGP10.phx.gbl...
> Hi John,
> it turns out that it was just a blip in the installation and wasnt that
> much of a one at that.
> It's all working properly now and I for one am really impressed with the
> performance increase we're getting across the board.
> Thanks for helping,
> Mike
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!

Saturday, February 25, 2012

64-Bit Installation of SQL Server 2005 on AMD Server

I have an 8-Processor AMD CPU box with Windows Server 2003 Enterprise (x64) R2 with SP1 installed.

How do I verify that I am installing the 64-Bit version of SQL Server 2005? I don't see any installer 'options' and when I view the list of SQL Server 2005 components in the Add/Remove program list there is nothing mentioned.

The source of my SQL Server 2005 installation code is the 'Ready Set Launch' DVD that Microsoft handed out when SQL Server 2005 was launched in 11/2005.

I haven't found any documentation to specifically details 64-bit installations.

Thank you.

...cordell...

The media itself must be the 64-bit version of SQL 2005. Since your AMD box will support both 32-bit and 64-bit versions, it's tough to tell what you're installing. After installing, the 64-bit versions have a "(64-bit)" tag on the end of them in Add/Remove Programs. My guess is that you have a copy of the 32-bit version.

Thanks,
Sam Lester (MSFT)

|||

Sam...

From what I can see I am installing the 32-bit versions of the SQL Server 2005 software on the AMD box.

I apologize for being pedantic here.....but I wanted to confirm that I will need to follow back up with my software vendor and order a 64-bit version of SQL Server 2005. (This is what I am concluding from your statements.)

After searching around the SKU I have is 228-05237 for this version...but I couldn't find anything in the SQL Server section of the MS website to confirm it. While I realize you are not in sales...what would the URL be for confirming the SKU on the media.

Thank you.

...cordell...

|||

No problem at all. You will need to contact your software vendor and specifically request the 64-bit version. I don't fully understand the licensing options for every situation, but I think this page will help you find the SKU/item number you are looking for. I have linked the Enterprise SKU's, but you can search for the others as well.

http://www.microsoft.com/PRODUCTS/info/product.aspx?view=22&pcid=d635228e-6aed-404b-9af1-7c27819c24e4&crumb=srch&qu=sql+server&gpid=c419977d-7963-4c38-8caf-95d3f779bed1

Example (make sure you pick the one that applies to you):

Full Version
Microsoft? SQL Server Enterprise Edition 2005 x64 English CD/DVD 25 Client
Item: 810-05188

Let me know if this is what you're looking for.

Thanks,
Sam

|||

Thank you Sam for the confirmation and assistance. That is what I was looking for.

...cordell...

64 bit silent Installation

Hi:

Is it possible to install a 64 bit SQL Server 2005 silently?. I am wondering what are the command options that are needed to do a quiet Install of Enterprise Edition of SQL Server 2005 (x64) on a x64 OS.

Any info is appreciated.

Thanks

Ankith

The 64-bit command line parameters are the same as the 32-bit parameters. Since your install configutation options are so vast, my suggestion would be to open up template.ini (found on any SQL install media) and take a look at the numerous silent install examples in that file. Or search Books Online for silent install instructions. If you have specific questions, let us know.

Thanks,
Sam Lester (MSFT)

Sunday, February 19, 2012

6.5 connectivity to 2000

Is it safe to use 6.5 connectivity on a 95 machine to
connect to a SQL 2000 installation on Win 2K?Hi,
No issues. You can execute all commands. Only demerit is that you wont get
the GUI facilities available in SQL 2000 client.
FYI, You cant use SQL 6.5 enterprise manager to connect to SQL 2000. Only
ISQLW can be used .
Hari
"Mark Walker" <anonymous@.discussions.microsoft.com> wrote in message
news:254101c3fc6a$25446c80$a101280a@.phx.gbl...
> Is it safe to use 6.5 connectivity on a 95 machine to
> connect to a SQL 2000 installation on Win 2K?|||... and since 6.5 ISQL.EXE and ISQLW.EXE uses DbLibrary, some of the new
stuff in 7.0/2000 will not be available. Such includes longer strings than
255 characters, Unicode, uniqueidentifier etc.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:%2387UBvG$DHA.2520@.TK2MSFTNGP11.phx.gbl...
> Hi,
> No issues. You can execute all commands. Only demerit is that you wont get
> the GUI facilities available in SQL 2000 client.
> FYI, You cant use SQL 6.5 enterprise manager to connect to SQL 2000. Only
> ISQLW can be used .
>
> Hari
> "Mark Walker" <anonymous@.discussions.microsoft.com> wrote in message
> news:254101c3fc6a$25446c80$a101280a@.phx.gbl...
> > Is it safe to use 6.5 connectivity on a 95 machine to
> > connect to a SQL 2000 installation on Win 2K?
>

6.5 connectivity to 2000

Is it safe to use 6.5 connectivity on a 95 machine to
connect to a SQL 2000 installation on Win 2K?Hi,
No issues. You can execute all commands. Only demerit is that you wont get
the GUI facilities available in SQL 2000 client.
FYI, You cant use SQL 6.5 enterprise manager to connect to SQL 2000. Only
ISQLW can be used .
Hari
"Mark Walker" <anonymous@.discussions.microsoft.com> wrote in message
news:254101c3fc6a$25446c80$a101280a@.phx.gbl...
> Is it safe to use 6.5 connectivity on a 95 machine to
> connect to a SQL 2000 installation on Win 2K?|||... and since 6.5 ISQL.EXE and ISQLW.EXE uses DbLibrary, some of the new
stuff in 7.0/2000 will not be available. Such includes longer strings than
255 characters, Unicode, uniqueidentifier etc.
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:%2387UBvG$DHA.2520@.TK2MSFTNGP11.phx.gbl...
> Hi,
> No issues. You can execute all commands. Only demerit is that you wont get
> the GUI facilities available in SQL 2000 client.
> FYI, You cant use SQL 6.5 enterprise manager to connect to SQL 2000. Only
> ISQLW can be used .
>
> Hari
> "Mark Walker" <anonymous@.discussions.microsoft.com> wrote in message
> news:254101c3fc6a$25446c80$a101280a@.phx.gbl...
>

Monday, March 19, 2012

8GB memory installation

8GB memory installation

8GB memory installation

Tuesday, March 6, 2012

64-bit SQL Server 2005 Installation (Reporting Services)

64bit SQl

64-bit problem

Saturday, February 25, 2012

64-Bit Installation of SQL Server 2005 on AMD Server

64 bit silent Installation

Sunday, February 19, 2012

6.5 connectivity to 2000

6.5 connectivity to 2000

3G ram for SQL server

Blog Archive

About Me