Showing posts with label sp1. Show all posts
Showing posts with label sp1. Show all posts

Monday, March 19, 2012

adding sqlexpress sp1/2 into setup project

Hi All,

How can I add sql server express sp1 or sp2 into a setup project I created for an application. Normally sqlserver express is a prerequisite for my app and in deployment vs only adds sqlexpress not the sqlexpress with sp1 or sp2. I know that I need those to make my application run on vista. Any suggestion?

Thanks

The prerequisites in VS are driven by a set of manifests installed with VS that only target SQL Express RTM. Microsoft has not released updates to these prerequisites, but you can build your own prerequisite for SQL Express SP2 by following the directions in the SQL Express blog. Check out the instructions here.

Mike

|||After a long wait I knew that you will reply. I haven't tried your instructions yet but I am sure this is the answer. Thanks for the reply.

adding sqlexpress sp1/2 into setup project

Hi All,

How can I add sql server express sp1 or sp2 into a setup project I created for an application. Normally sqlserver express is a prerequisite for my app and in deployment vs only adds sqlexpress not the sqlexpress with sp1 or sp2. I know that I need those to make my application run on vista. Any suggestion?

Thanks

The prerequisites in VS are driven by a set of manifests installed with VS that only target SQL Express RTM. Microsoft has not released updates to these prerequisites, but you can build your own prerequisite for SQL Express SP2 by following the directions in the SQL Express blog. Check out the instructions here.

Mike

|||After a long wait I knew that you will reply. I haven't tried your instructions yet but I am sure this is the answer. Thanks for the reply.

Adding SQL Reporting Services to SQL Server 2005 SP1

I'm using Reporting Services Configuration tool to add the Reporting and ReportingTemb databases. Once the have been created, the tool attempts to upgrade the databases and can not create a script. This are the errors I see from the from the Reporting Services Configuration Tool after creating the databases:

! Verifing Database Version

The Database version (C.0.8.40) does not match your Reporting Services installation. You must upgrade your Reporting Services database.

! Creating upgrade script for database version C.0.8.40

ReportServicesConfigUI.WMIProvider.WMIProviderException: The version does not match a supported version.


at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.GenerateDatabaseUpgradeScript(String databaseName, String serverVersion, String& script)

I've reinstalled the entire SQL Server 2005 installation. As part of company installation precodure, SQL 2005 w/o Reporting Services is installed first, followed by SP1. I then perform the SQL Reporting Services installation add-on.

Thanks,

Mark

Ditto. I'm having the same issue. Another wrinkle (or red herring) is that I changed the name of the server before installing SP1 and before installing Reporting Services.|||I get the same too. This is a fresh intall of SQL 2005. What gives!|||

Found the answer :)

Just install SQL 2005 SP1 again (after you installed Reports Services). Fixed it for me.

Good luck

|||

That may do it as well. I re-installed SQL Server because I believe the issue was that I had the retail version of SQL 2005 installed and was trying to install the Developer Edition of SQL 2005 Reporting Services on that. I got a vague warning about the versions not matching, but matching the version of SQL 2005 between the database engine and the reporting services fixed the issue. I still need to install SP1 again....

|||

Yes. Reapplying SP1 after the Reporting Services install fixed the problem. Once SP1 is applied, run the Reporting Services Configuration Tool and the older database format will be converted.

- Thanks for the help.

|||

Hello,

I am receiving the error, "creating upgrade script for database version c.0.8.40" as well. I've tried everything I know of and it still doesn't work. I've uninstalled SQL Reporting Services, reinstalled, then reapplied SP1 but it still doesn't work. I've tried changing the application app pool for reporting services, that didn't work. I've also traced the process with file mon, that didn't help (saw a post on that somewhere else).

Can anyone help me? Is there a utility to check the health of reporting services maybe?

Thanks,
Bob

|||

I can't remember how I solved the issue now (a while ago)

possibly the worst case, uninstall everything and re-install everything

With SP2 officially out, you might want to try upgrade everything (RS, SQL) to SP2 then

|||

Hi Bob,

Try installing SQL server SP2,this should be working.

i did the same and lol its as working fine

Thanks,

vvbkumar

Adding SQL Reporting Services to SQL Server 2005 SP1

I'm using Reporting Services Configuration tool to add the Reporting and ReportingTemb databases. Once the have been created, the tool attempts to upgrade the databases and can not create a script. This are the errors I see from the from the Reporting Services Configuration Tool after creating the databases:

! Verifing Database Version

The Database version (C.0.8.40) does not match your Reporting Services installation. You must upgrade your Reporting Services database.

! Creating upgrade script for database version C.0.8.40

ReportServicesConfigUI.WMIProvider.WMIProviderException: The version does not match a supported version.


at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.GenerateDatabaseUpgradeScript(String databaseName, String serverVersion, String& script)

I've reinstalled the entire SQL Server 2005 installation. As part of company installation precodure, SQL 2005 w/o Reporting Services is installed first, followed by SP1. I then perform the SQL Reporting Services installation add-on.

Thanks,

Mark

Ditto. I'm having the same issue. Another wrinkle (or red herring) is that I changed the name of the server before installing SP1 and before installing Reporting Services.|||I get the same too. This is a fresh intall of SQL 2005. What gives!|||

Found the answer :)

Just install SQL 2005 SP1 again (after you installed Reports Services). Fixed it for me.

Good luck

|||

That may do it as well. I re-installed SQL Server because I believe the issue was that I had the retail version of SQL 2005 installed and was trying to install the Developer Edition of SQL 2005 Reporting Services on that. I got a vague warning about the versions not matching, but matching the version of SQL 2005 between the database engine and the reporting services fixed the issue. I still need to install SP1 again....

|||

Yes. Reapplying SP1 after the Reporting Services install fixed the problem. Once SP1 is applied, run the Reporting Services Configuration Tool and the older database format will be converted.

- Thanks for the help.

|||

Hello,

I am receiving the error, "creating upgrade script for database version c.0.8.40" as well. I've tried everything I know of and it still doesn't work. I've uninstalled SQL Reporting Services, reinstalled, then reapplied SP1 but it still doesn't work. I've tried changing the application app pool for reporting services, that didn't work. I've also traced the process with file mon, that didn't help (saw a post on that somewhere else).

Can anyone help me? Is there a utility to check the health of reporting services maybe?

Thanks,
Bob

|||

I can't remember how I solved the issue now (a while ago)

possibly the worst case, uninstall everything and re-install everything

With SP2 officially out, you might want to try upgrade everything (RS, SQL) to SP2 then

|||

Hi Bob,

Try installing SQL server SP2,this should be working.

i did the same and lol its as working fine

Thanks,

vvbkumar

Adding SQL Reporting Services to SQL Server 2005 SP1

I'm using Reporting Services Configuration tool to add the Reporting and ReportingTemb databases. Once the have been created, the tool attempts to upgrade the databases and can not create a script. This are the errors I see from the from the Reporting Services Configuration Tool after creating the databases:

! Verifing Database Version

The Database version (C.0.8.40) does not match your Reporting Services installation. You must upgrade your Reporting Services database.

! Creating upgrade script for database version C.0.8.40

ReportServicesConfigUI.WMIProvider.WMIProviderException: The version does not match a supported version.


at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.GenerateDatabaseUpgradeScript(String databaseName, String serverVersion, String& script)

I've reinstalled the entire SQL Server 2005 installation. As part of company installation precodure, SQL 2005 w/o Reporting Services is installed first, followed by SP1. I then perform the SQL Reporting Services installation add-on.

Thanks,

Mark

Ditto. I'm having the same issue. Another wrinkle (or red herring) is that I changed the name of the server before installing SP1 and before installing Reporting Services.|||I get the same too. This is a fresh intall of SQL 2005. What gives!|||

Found the answer :)

Just install SQL 2005 SP1 again (after you installed Reports Services). Fixed it for me.

Good luck

|||

That may do it as well. I re-installed SQL Server because I believe the issue was that I had the retail version of SQL 2005 installed and was trying to install the Developer Edition of SQL 2005 Reporting Services on that. I got a vague warning about the versions not matching, but matching the version of SQL 2005 between the database engine and the reporting services fixed the issue. I still need to install SP1 again....

|||

Yes. Reapplying SP1 after the Reporting Services install fixed the problem. Once SP1 is applied, run the Reporting Services Configuration Tool and the older database format will be converted.

- Thanks for the help.

|||

Hello,

I am receiving the error, "creating upgrade script for database version c.0.8.40" as well. I've tried everything I know of and it still doesn't work. I've uninstalled SQL Reporting Services, reinstalled, then reapplied SP1 but it still doesn't work. I've tried changing the application app pool for reporting services, that didn't work. I've also traced the process with file mon, that didn't help (saw a post on that somewhere else).

Can anyone help me? Is there a utility to check the health of reporting services maybe?

Thanks,
Bob

|||

I can't remember how I solved the issue now (a while ago)

possibly the worst case, uninstall everything and re-install everything

With SP2 officially out, you might want to try upgrade everything (RS, SQL) to SP2 then

|||

Hi Bob,

Try installing SQL server SP2,this should be working.

i did the same and lol its as working fine

Thanks,

vvbkumar

Sunday, March 11, 2012

Adding Reporting Services to an existing SP1 install

HI,

Is there an easy way to install reporting services on a machine that is already running sp1? When I initially isntalled Sql Server I did not install ssrs. Now, SP1 is installed and when I run the setup tool to install ssrs, it warns me regarding a "version change", presumablly because my media is not sp1, but RTM. Any ideas?

1. Install RS from RTM media

2. Apply SP1 on RS.

Thursday, March 8, 2012

Adding new node to SQL SP4 cluster

Hi all,
I'm trying to add a new node to our SQL Server 2000 SP4 cluster. Cluster
node is Windows 2003 SP1. I can add the node to the SQL cluster, but when I
try to add SP4 to the new node, I get an error message when I enter in the
service password for the instance.
Error message : Setup cannot verify/grant logon as service right to the SQL
Server service logon account: 5000 (0x1388)
However, this error didn't come up when I was adding the node to the SQL
cluster and it prompted me for the same password. We're running an
active/active configuration and I can't do anything with the other instance
(the default one) as it says that this instance is still waiting for the
service pack!
Any ideas anyone? Thanks in advance
Dave
Dave Wall
Dave,
It looks like a permission issue. Does the Windows domain a/c that you are using the setup have local admin privileges on both the cluster nodes? Try running the setup using the virtual SQL Server service a/c or the
cluster service a/c ?
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Dave,
Are you using the NEED_SP_KEY in the registry. If yes, then remove this key and re-run SP4 from the original node (i.e the node that is already on SP4 and owns the SQL resources) and see if this helps?
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Thanks Uttam,
removed the reg key and it all went through without any problems
Dave
Dave Wall
"Uttam Parui[MS]" wrote:

> Dave,
> Are you using the NEED_SP_KEY in the registry. If yes, then remove this key and re-run SP4 from the original node (i.e the node that is already on SP4 and owns the SQL resources) and see if this helps?
> Best Regards,
> Uttam Parui
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
> Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
> http://www.microsoft.com/protect
> http://www.microsoft.com/security/guidance/default.mspx
>
>
|||Dave,
Glad to hear that the issue is resolved. I appreciate your update.
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Hello, I'm having the same problem, but I don't know what you mean by this
NEED_SP_KEY I can't find any information on it. If you could shed some light
on this I would greatly appreciate it!
--Gene
"Uttam Parui[MS]" <uttamkp@.online.microsoft.com> wrote in message
news:KA3IUo6kFHA.944@.TK2MSFTNGXA01.phx.gbl...
> Dave,
> Are you using the NEED_SP_KEY in the registry. If yes, then remove this
key and re-run SP4 from the original node (i.e the node that is already on
SP4 and owns the SQL resources) and see if this helps?
> Best Regards,
> Uttam Parui
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
> Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
> http://www.microsoft.com/protect
> http://www.microsoft.com/security/guidance/default.mspx
>
|||Depending on certain parameters, the Need_SP_Key is added to the new node by the setup process when the node is
added to the SQL failover cluster.
Check (on all nodes) if you have the following key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\80\Need_SP_Key
If yes, then delete it. Then try to install the service pack 4 from the active node where SQL Server is currently running.
If no, then you might be having a different issue. Give more details for us to help you.
HTH,
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way
to do this is to visit the following websites: http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Uttam Parui[MS] wrote:
> Dave,
> Are you using the NEED_SP_KEY in the registry. If yes, then remove this key and re-run SP4 from the original node (i.e the node that is already on SP4 and owns the SQL resources) and see if this helps?
For me this does not realy help. The node needs to be a possible owner of
the sql resources or else, the node is not updated. When you have just added
the node by the advanced sql setup option, this is not the case yet.
The second problem is, that this way sp4 updates all the nodes and takes the
SQL resources OFFLINE.
I tried installing SP3 first, which is not a goed idea. The sqlsetup runs
fine, the node becomes a possible owner but can't be used (sql wil not come
online), the NEED_SP_KEY dissapears, with means SP4 wants to reapply totaly.
Restoring the NEED_SP_KEY solves this but then the "Setup cannot
verify/grant logon as service right..." is back.
So adding a SP4 node without takeing SQL temporarily offline is not possible.
Hans
p.s.
SP4 was installed with a enterprise admin account.
|||There is a hotfix available from Microsoft support which fixed this for me.
See http://support.microsoft.com/?kbid=905286
BB.
"Hans de Bruin" wrote:

> Uttam Parui[MS] wrote:
> For me this does not realy help. The node needs to be a possible owner of
> the sql resources or else, the node is not updated. When you have just added
> the node by the advanced sql setup option, this is not the case yet.
> The second problem is, that this way sp4 updates all the nodes and takes the
> SQL resources OFFLINE.
> I tried installing SP3 first, which is not a goed idea. The sqlsetup runs
> fine, the node becomes a possible owner but can't be used (sql wil not come
> online), the NEED_SP_KEY dissapears, with means SP4 wants to reapply totaly.
> Restoring the NEED_SP_KEY solves this but then the "Setup cannot
> verify/grant logon as service right..." is back.
> So adding a SP4 node without takeing SQL temporarily offline is not possible.
> --
> Hans
> p.s.
> SP4 was installed with a enterprise admin account.
>

Tuesday, March 6, 2012

Adding more RAM for MS SQL Server 2000

Hi
I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at my
hand. The SQL Server is configured for dynamic memory allocation. The machine
had 2GB of RAM in it when I installed the SQL Server. Now I've installed two
more gigabytes of RAM into the machine and I want to allow the SQL Server to
use a total of 3GB of RAM (by means of turning on the /3GB switch in Windows
boot.ini).
Do I also have to reconfigure any SQL Server parameters after enabling it to
use the additional gigabyte of RAM?
Many thanks,
Oskar
No. All you have to do is add the /3GB switch to boot.ini and reboot.
If you wanted to address > 4GB of RAM then you would have to start
playing with AWE but <= 4GB is addressable with normal windows memory
addressing & therefore normal MSSQL dynamic memory management.
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
Oskar wrote:

>Hi
>I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at my
>hand. The SQL Server is configured for dynamic memory allocation. The machine
>had 2GB of RAM in it when I installed the SQL Server. Now I've installed two
>more gigabytes of RAM into the machine and I want to allow the SQL Server to
>use a total of 3GB of RAM (by means of turning on the /3GB switch in Windows
>boot.ini).
>Do I also have to reconfigure any SQL Server parameters after enabling it to
>use the additional gigabyte of RAM?
>--
>Many thanks,
>Oskar
>
>
|||Hi,
This will work out if your SQL server 2000 edition is Enterprise or Developer. Standard edition can support a maximum of 2 GB only.
Thanks
Hari
SQL Server MVP
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message news:OvpsIwbZFHA.4088@.TK2MSFTNGP15.phx.gbl...
No. All you have to do is add the /3GB switch to boot.ini and reboot. If you wanted to address > 4GB of RAM then you would have to start playing with AWE but <= 4GB is addressable with normal windows memory addressing & therefore normal MSSQL dynamic memory management.
mike hodgson | database administrator | mallesons stephen jaques
T +61 (2) 9296 3668 | F +61 (2) 9296 3885 | M +61 (408) 675 907
E mailto:mike.hodgson@.mallesons.nospam.com | W http://www.mallesons.com
Oskar wrote:
Hi
I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at my
hand. The SQL Server is configured for dynamic memory allocation. The machine
had 2GB of RAM in it when I installed the SQL Server. Now I've installed two
more gigabytes of RAM into the machine and I want to allow the SQL Server to
use a total of 3GB of RAM (by means of turning on the /3GB switch in Windows
boot.ini).
Do I also have to reconfigure any SQL Server parameters after enabling it to
use the additional gigabyte of RAM?
Many thanks,
Oskar

Adding more RAM for MS SQL Server 2000

Hi
I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at my
hand. The SQL Server is configured for dynamic memory allocation. The machine
had 2GB of RAM in it when I installed the SQL Server. Now I've installed two
more gigabytes of RAM into the machine and I want to allow the SQL Server to
use a total of 3GB of RAM (by means of turning on the /3GB switch in Windows
boot.ini).
Do I also have to reconfigure any SQL Server parameters after enabling it to
use the additional gigabyte of RAM?
--
Many thanks,
OskarThis is a multi-part message in MIME format.
--060508000204080606090209
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
No. All you have to do is add the /3GB switch to boot.ini and reboot.
If you wanted to address > 4GB of RAM then you would have to start
playing with AWE but <= 4GB is addressable with normal windows memory
addressing & therefore normal MSSQL dynamic memory management.
--
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
Oskar wrote:
>Hi
>I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at my
>hand. The SQL Server is configured for dynamic memory allocation. The machine
>had 2GB of RAM in it when I installed the SQL Server. Now I've installed two
>more gigabytes of RAM into the machine and I want to allow the SQL Server to
>use a total of 3GB of RAM (by means of turning on the /3GB switch in Windows
>boot.ini).
>Do I also have to reconfigure any SQL Server parameters after enabling it to
>use the additional gigabyte of RAM?
>--
>Many thanks,
>Oskar
>
>
--060508000204080606090209
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>No. All you have to do is add the /3GB switch to boot.ini and
reboot. If you wanted to address > 4GB of RAM then you would have
to start playing with AWE but <= 4GB is addressable with normal
windows memory addressing & therefore normal MSSQL dynamic memory
management.</tt><br>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font> </span><b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"> <font face="Tahoma"
size="2">|</font><i><font face="Tahoma"> </font><font face="Tahoma"
size="2"> database administrator</font></i><font face="Tahoma" size="2">
| mallesons</font><font face="Tahoma"> </font><font face="Tahoma"
size="2">stephen</font><font face="Tahoma"> </font><font face="Tahoma"
size="2"> jaques</font><font face="Tahoma"><br>
</font><b><font face="Tahoma" size="2">T</font></b><font face="Tahoma"
size="2"> +61 (2) 9296 3668 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2"> F</font></b><font face="Tahoma" size="2"> +61
(2) 9296 3885 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2">M</font></b><font face="Tahoma" size="2"> +61
(408) 675 907</font><br>
<b><font face="Tahoma" size="2">E</font></b><font face="Tahoma" size="2">
<a href="http://links.10026.com/?link=mailto:mike.hodgson@.mallesons.nospam.com">
mailto:mike.hodgson@.mallesons.nospam.com</a> |</font><b><font
face="Tahoma"> </font><font face="Tahoma" size="2">W</font></b><font
face="Tahoma" size="2"> <a href="http://links.10026.com/?link=/">http://www.mallesons.com">
http://www.mallesons.com</a></font></span> </p>
</div>
<br>
<br>
Oskar wrote:
<blockquote cite="midDA9DCAEE-A7F3-4E04-986C-97D1E43CDE91@.microsoft.com"
type="cite">
<pre wrap="">Hi
I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at my
hand. The SQL Server is configured for dynamic memory allocation. The machine
had 2GB of RAM in it when I installed the SQL Server. Now I've installed two
more gigabytes of RAM into the machine and I want to allow the SQL Server to
use a total of 3GB of RAM (by means of turning on the /3GB switch in Windows
boot.ini).
Do I also have to reconfigure any SQL Server parameters after enabling it to
use the additional gigabyte of RAM?
--
Many thanks,
Oskar
</pre>
</blockquote>
</body>
</html>
--060508000204080606090209--|||This is a multi-part message in MIME format.
--=_NextPart_000_004D_01C565EC.8E52DE90
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Hi,
This will work out if your SQL server 2000 edition is Enterprise or =Developer. Standard edition can support a maximum of 2 GB only.
Thanks
Hari
SQL Server MVP
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message =news:OvpsIwbZFHA.4088@.TK2MSFTNGP15.phx.gbl...
No. All you have to do is add the /3GB switch to boot.ini and reboot. = If you wanted to address > 4GB of RAM then you would have to start =playing with AWE but <=3D 4GB is addressable with normal windows memory =addressing & therefore normal MSSQL dynamic memory management.
--
mike hodgson | database administrator | mallesons stephen jaques
T +61 (2) 9296 3668 | F +61 (2) 9296 3885 | M +61 (408) 675 907
E mailto:mike.hodgson@.mallesons.nospam.com | W =http://www.mallesons.com=20
Oskar wrote: Hi
I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at =my hand. The SQL Server is configured for dynamic memory allocation. The =machine had 2GB of RAM in it when I installed the SQL Server. Now I've installed =two more gigabytes of RAM into the machine and I want to allow the SQL =Server to use a total of 3GB of RAM (by means of turning on the /3GB switch in =Windows boot.ini).
Do I also have to reconfigure any SQL Server parameters after enabling =it to use the additional gigabyte of RAM?
--
Many thanks,
Oskar
--=_NextPart_000_004D_01C565EC.8E52DE90
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

Hi,
This will work out if your SQL server =2000 edition is Enterprise or Developer. Standard edition can support a maximum of 2 =GB only.
Thanks
Hari
SQL Server MVP
"Mike Hodgson" wrote in message news:OvpsIwbZFHA.4088=@.TK2MSFTNGP15.phx.gbl...No. All you have to do is add the /3GB switch to boot.ini and =reboot. If you wanted to address > 4GB of RAM then you would have to start playing =with AWE but <=3D 4GB is addressable with normal windows memory =addressing & therefore normal MSSQL dynamic memory management.
--mike =hodgson | database =administrator | mallesons =stephen jaquesT +61 (2) 9296 3668 | F +61 (2) 9296 3885 | M +61 (408) 675 907E mailto:mike.hodgson@.mal=lesons.nospam.com | W http://www.mallesons.com Oskar wrote: Hi
I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at =my hand. The SQL Server is configured for dynamic memory allocation. The =machine had 2GB of RAM in it when I installed the SQL Server. Now I've installed =two more gigabytes of RAM into the machine and I want to allow the SQL =Server to use a total of 3GB of RAM (by means of turning on the /3GB switch in =Windows boot.ini).
Do I also have to reconfigure any SQL Server parameters after enabling =it to use the additional gigabyte of RAM?
--
Many thanks,
Oskar


--=_NextPart_000_004D_01C565EC.8E52DE90--

Adding more RAM for MS SQL Server 2000

Hi
I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at my
hand. The SQL Server is configured for dynamic memory allocation. The machin
e
had 2GB of RAM in it when I installed the SQL Server. Now I've installed two
more gigabytes of RAM into the machine and I want to allow the SQL Server to
use a total of 3GB of RAM (by means of turning on the /3GB switch in Windows
boot.ini).
Do I also have to reconfigure any SQL Server parameters after enabling it to
use the additional gigabyte of RAM?
Many thanks,
OskarNo. All you have to do is add the /3GB switch to boot.ini and reboot.
If you wanted to address > 4GB of RAM then you would have to start
playing with AWE but <= 4GB is addressable with normal windows memory
addressing & therefore normal MSSQL dynamic memory management.
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
Oskar wrote:

>Hi
>I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at my
>hand. The SQL Server is configured for dynamic memory allocation. The machi
ne
>had 2GB of RAM in it when I installed the SQL Server. Now I've installed tw
o
>more gigabytes of RAM into the machine and I want to allow the SQL Server t
o
>use a total of 3GB of RAM (by means of turning on the /3GB switch in Window
s
>boot.ini).
>Do I also have to reconfigure any SQL Server parameters after enabling it t
o
>use the additional gigabyte of RAM?
>--
>Many thanks,
>Oskar
>
>|||Hi,
This will work out if your SQL server 2000 edition is Enterprise or Develope
r. Standard edition can support a maximum of 2 GB only.
Thanks
Hari
SQL Server MVP
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message news:Ovp
sIwbZFHA.4088@.TK2MSFTNGP15.phx.gbl...
No. All you have to do is add the /3GB switch to boot.ini and reboot. If yo
u wanted to address > 4GB of RAM then you would have to start playing with A
WE but <= 4GB is addressable with normal windows memory addressing & therefo
re normal MSSQL dynamic memory management.
mike hodgson | database administrator | mallesons stephen jaques
T +61 (2) 9296 3668 | F +61 (2) 9296 3885 | M +61 (408) 675 907
E mailto:mike.hodgson@.mallesons.nospam.com | W http://www.mallesons.com
Oskar wrote:
Hi
I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at my
hand. The SQL Server is configured for dynamic memory allocation. The machin
e
had 2GB of RAM in it when I installed the SQL Server. Now I've installed two
more gigabytes of RAM into the machine and I want to allow the SQL Server to
use a total of 3GB of RAM (by means of turning on the /3GB switch in Windows
boot.ini).
Do I also have to reconfigure any SQL Server parameters after enabling it to
use the additional gigabyte of RAM?
Many thanks,
Oskar