sql server db: 2gb

Showing posts with label 2gb. Show all posts

Tuesday, March 27, 2012

Correct Memory Configuration for 4GB/W2K3 Enterprise

Hello all,
I have a SQL2000 installation with Windows2003 Enterprise and 4 GB of system
memory. SQL never uses more than 2GB of system memory. What is the correct
configuration of the 3GB and PAE switches in the boot.ini file?
--
Roy Love
SupportOnline.BIZRoy,
From the SQL BOL:
To enable Windows 2000 Advanced Server and Windows 2000 Datacenter Server to
support a 3-GB virtual address space, you must add the /3gb parameter to the
boot.ini file. This allows user applications to address 3 GB of virtual
memory and reserves 1 GB of virtual memory for the operating system.
HTH
Jerry
"RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
news:0F55F3B8-39E0-4C82-8C51-189DC271D915@.microsoft.com...
> Hello all,
> I have a SQL2000 installation with Windows2003 Enterprise and 4 GB of
> system
> memory. SQL never uses more than 2GB of system memory. What is the
> correct
> configuration of the 3GB and PAE switches in the boot.ini file?
> --
> Roy Love
> SupportOnline.BIZ|||I am running Windows2003 Server Enterprise, not 2K. SQL also mentions
setting AWE to the amount of memory in the server. You mentioned virtural
memory, I am talking about physical memory.
thanks,
--
Roy Love
SupportOnline.BIZ
"Jerry Spivey" wrote:
> Roy,
> From the SQL BOL:
> To enable Windows 2000 Advanced Server and Windows 2000 Datacenter Server to
> support a 3-GB virtual address space, you must add the /3gb parameter to the
> boot.ini file. This allows user applications to address 3 GB of virtual
> memory and reserves 1 GB of virtual memory for the operating system.
> HTH
> Jerry
> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
> news:0F55F3B8-39E0-4C82-8C51-189DC271D915@.microsoft.com...
> > Hello all,
> >
> > I have a SQL2000 installation with Windows2003 Enterprise and 4 GB of
> > system
> > memory. SQL never uses more than 2GB of system memory. What is the
> > correct
> > configuration of the 3GB and PAE switches in the boot.ini file?
> > --
> > Roy Love
> > SupportOnline.BIZ
>
>|||Roy,
Might take a look at:
http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech
and
http://support.microsoft.com/kb/283037/
HTH
Jerry
"RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
news:98937CC7-FA07-4952-951A-132FD41E23F6@.microsoft.com...
>I am running Windows2003 Server Enterprise, not 2K. SQL also mentions
> setting AWE to the amount of memory in the server. You mentioned virtural
> memory, I am talking about physical memory.
> thanks,
> --
> Roy Love
> SupportOnline.BIZ
>
> "Jerry Spivey" wrote:
>> Roy,
>> From the SQL BOL:
>> To enable Windows 2000 Advanced Server and Windows 2000 Datacenter Server
>> to
>> support a 3-GB virtual address space, you must add the /3gb parameter to
>> the
>> boot.ini file. This allows user applications to address 3 GB of virtual
>> memory and reserves 1 GB of virtual memory for the operating system.
>> HTH
>> Jerry
>> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
>> news:0F55F3B8-39E0-4C82-8C51-189DC271D915@.microsoft.com...
>> > Hello all,
>> >
>> > I have a SQL2000 installation with Windows2003 Enterprise and 4 GB of
>> > system
>> > memory. SQL never uses more than 2GB of system memory. What is the
>> > correct
>> > configuration of the 3GB and PAE switches in the boot.ini file?
>> > --
>> > Roy Love
>> > SupportOnline.BIZ
>>|||If you are using SQL Server 2000 SE, then SQL Server will not use > 2GB memory. I think that 2Gb is
for the buffer pool (data cache, cached plans etc), and MemToLeave area is outside of that. So,
*possibly* you could tweak out a bit more using PAE and AWE:
Today (roughly):
BP: 1.7 GB
MemToLeave: 0.3 GB
With AWE and PAE:
BP: 2 GB
MemToLeave 0.3 GB
Here's a good place to learn more about how SQL Server uses memory, AWE etc.:
http://blogs.msdn.com/slavao/
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
news:98937CC7-FA07-4952-951A-132FD41E23F6@.microsoft.com...
>I am running Windows2003 Server Enterprise, not 2K. SQL also mentions
> setting AWE to the amount of memory in the server. You mentioned virtural
> memory, I am talking about physical memory.
> thanks,
> --
> Roy Love
> SupportOnline.BIZ
>
> "Jerry Spivey" wrote:
>> Roy,
>> From the SQL BOL:
>> To enable Windows 2000 Advanced Server and Windows 2000 Datacenter Server to
>> support a 3-GB virtual address space, you must add the /3gb parameter to the
>> boot.ini file. This allows user applications to address 3 GB of virtual
>> memory and reserves 1 GB of virtual memory for the operating system.
>> HTH
>> Jerry
>> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
>> news:0F55F3B8-39E0-4C82-8C51-189DC271D915@.microsoft.com...
>> > Hello all,
>> >
>> > I have a SQL2000 installation with Windows2003 Enterprise and 4 GB of
>> > system
>> > memory. SQL never uses more than 2GB of system memory. What is the
>> > correct
>> > configuration of the 3GB and PAE switches in the boot.ini file?
>> > --
>> > Roy Love
>> > SupportOnline.BIZ
>>|||Is Windows seeing the full 4GB?
Some raid cards (hot swap pci etc) can "steal" some memory unless you use
/PAE.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23BPfWr70FHA.3376@.TK2MSFTNGP14.phx.gbl...
> If you are using SQL Server 2000 SE, then SQL Server will not use > 2GB
> memory. I think that 2Gb is for the buffer pool (data cache, cached plans
> etc), and MemToLeave area is outside of that. So, *possibly* you could
> tweak out a bit more using PAE and AWE:
> Today (roughly):
> BP: 1.7 GB
> MemToLeave: 0.3 GB
> With AWE and PAE:
> BP: 2 GB
> MemToLeave 0.3 GB
> Here's a good place to learn more about how SQL Server uses memory, AWE
> etc.: http://blogs.msdn.com/slavao/
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
> news:98937CC7-FA07-4952-951A-132FD41E23F6@.microsoft.com...
>>I am running Windows2003 Server Enterprise, not 2K. SQL also mentions
>> setting AWE to the amount of memory in the server. You mentioned
>> virtural
>> memory, I am talking about physical memory.
>> thanks,
>> --
>> Roy Love
>> SupportOnline.BIZ
>>
>> "Jerry Spivey" wrote:
>> Roy,
>> From the SQL BOL:
>> To enable Windows 2000 Advanced Server and Windows 2000 Datacenter
>> Server to
>> support a 3-GB virtual address space, you must add the /3gb parameter to
>> the
>> boot.ini file. This allows user applications to address 3 GB of virtual
>> memory and reserves 1 GB of virtual memory for the operating system.
>> HTH
>> Jerry
>> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
>> news:0F55F3B8-39E0-4C82-8C51-189DC271D915@.microsoft.com...
>> > Hello all,
>> >
>> > I have a SQL2000 installation with Windows2003 Enterprise and 4 GB of
>> > system
>> > memory. SQL never uses more than 2GB of system memory. What is the
>> > correct
>> > configuration of the 3GB and PAE switches in the boot.ini file?
>> > --
>> > Roy Love
>> > SupportOnline.BIZ
>>
>|||Thanks Tibor,
I am running SQL2000 Enterprise Edition, not SE.
Regards,
--
Roy Love
SupportOnline.BIZ
"Tibor Karaszi" wrote:
> If you are using SQL Server 2000 SE, then SQL Server will not use > 2GB memory. I think that 2Gb is
> for the buffer pool (data cache, cached plans etc), and MemToLeave area is outside of that. So,
> *possibly* you could tweak out a bit more using PAE and AWE:
> Today (roughly):
> BP: 1.7 GB
> MemToLeave: 0.3 GB
> With AWE and PAE:
> BP: 2 GB
> MemToLeave 0.3 GB
> Here's a good place to learn more about how SQL Server uses memory, AWE etc.:
> http://blogs.msdn.com/slavao/
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
> news:98937CC7-FA07-4952-951A-132FD41E23F6@.microsoft.com...
> >I am running Windows2003 Server Enterprise, not 2K. SQL also mentions
> > setting AWE to the amount of memory in the server. You mentioned virtural
> > memory, I am talking about physical memory.
> >
> > thanks,
> > --
> > Roy Love
> > SupportOnline.BIZ
> >
> >
> > "Jerry Spivey" wrote:
> >
> >> Roy,
> >>
> >> From the SQL BOL:
> >>
> >> To enable Windows 2000 Advanced Server and Windows 2000 Datacenter Server to
> >> support a 3-GB virtual address space, you must add the /3gb parameter to the
> >> boot.ini file. This allows user applications to address 3 GB of virtual
> >> memory and reserves 1 GB of virtual memory for the operating system.
> >>
> >> HTH
> >>
> >> Jerry
> >> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
> >> news:0F55F3B8-39E0-4C82-8C51-189DC271D915@.microsoft.com...
> >> > Hello all,
> >> >
> >> > I have a SQL2000 installation with Windows2003 Enterprise and 4 GB of
> >> > system
> >> > memory. SQL never uses more than 2GB of system memory. What is the
> >> > correct
> >> > configuration of the 3GB and PAE switches in the boot.ini file?
> >> > --
> >> > Roy Love
> >> > SupportOnline.BIZ
> >>
> >>
> >>
>|||Then you need either the /3GB switch or PAE and AWE. Aside, all memory in Windows is virtual memory,
An application doesn't address memory directly, it goes by the OS memory manager. Here's a start:
http://support.microsoft.com/default.aspx?scid=kb;en-us;274750
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
news:76402F72-A1B6-466F-802F-234A1033E0AE@.microsoft.com...
> Thanks Tibor,
> I am running SQL2000 Enterprise Edition, not SE.
> Regards,
> --
> Roy Love
> SupportOnline.BIZ
>
> "Tibor Karaszi" wrote:
>> If you are using SQL Server 2000 SE, then SQL Server will not use > 2GB memory. I think that 2Gb
>> is
>> for the buffer pool (data cache, cached plans etc), and MemToLeave area is outside of that. So,
>> *possibly* you could tweak out a bit more using PAE and AWE:
>> Today (roughly):
>> BP: 1.7 GB
>> MemToLeave: 0.3 GB
>> With AWE and PAE:
>> BP: 2 GB
>> MemToLeave 0.3 GB
>> Here's a good place to learn more about how SQL Server uses memory, AWE etc.:
>> http://blogs.msdn.com/slavao/
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
>> news:98937CC7-FA07-4952-951A-132FD41E23F6@.microsoft.com...
>> >I am running Windows2003 Server Enterprise, not 2K. SQL also mentions
>> > setting AWE to the amount of memory in the server. You mentioned virtural
>> > memory, I am talking about physical memory.
>> >
>> > thanks,
>> > --
>> > Roy Love
>> > SupportOnline.BIZ
>> >
>> >
>> > "Jerry Spivey" wrote:
>> >
>> >> Roy,
>> >>
>> >> From the SQL BOL:
>> >>
>> >> To enable Windows 2000 Advanced Server and Windows 2000 Datacenter Server to
>> >> support a 3-GB virtual address space, you must add the /3gb parameter to the
>> >> boot.ini file. This allows user applications to address 3 GB of virtual
>> >> memory and reserves 1 GB of virtual memory for the operating system.
>> >>
>> >> HTH
>> >>
>> >> Jerry
>> >> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
>> >> news:0F55F3B8-39E0-4C82-8C51-189DC271D915@.microsoft.com...
>> >> > Hello all,
>> >> >
>> >> > I have a SQL2000 installation with Windows2003 Enterprise and 4 GB of
>> >> > system
>> >> > memory. SQL never uses more than 2GB of system memory. What is the
>> >> > correct
>> >> > configuration of the 3GB and PAE switches in the boot.ini file?
>> >> > --
>> >> > Roy Love
>> >> > SupportOnline.BIZ
>> >>
>> >>
>> >>
>>

Correct Memory Configuration for 4GB/W2K3 Enterprise

Sunday, March 11, 2012

Copying database to new name on same server

Dear Y'all -
I'm a newbie to this list. I have a database of about 2Gb that I need
to duplicate several times, giving each duplicate a new name, on to a
single server. Sounds simple is proving to not be so. The basic
export command seems to do what I want but it runs for longer than I'm
willing to wait, over 6 hours. It takes less than an hour to create
the database from scratch.
Is there something I'm missing? Is there a way to duplicate a
database at the file system level and them update the DBMS system
tables (or whatever) so the new files are recognized properly.
TIA.
Yours - Billy
============================================================ William Goedicke goedicke@.goedsole.com
http://www.goedsole.com:8080
============================================================
Lest we forget:
Don't force it; get a bigger hammer.
- Al DodgeDo a backup once, then do multiple restores (during a restore you can
specify a new name, and it will take care of data file names etc. as well).
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"William Goedicke" <wgoedick@.reveregroup.com> wrote in message
news:m38ylcofqg.fsf@.mail.goedsole.com...
> Dear Y'all -
> I'm a newbie to this list. I have a database of about 2Gb that I need
> to duplicate several times, giving each duplicate a new name, on to a
> single server. Sounds simple is proving to not be so. The basic
> export command seems to do what I want but it runs for longer than I'm
> willing to wait, over 6 hours. It takes less than an hour to create
> the database from scratch.
> Is there something I'm missing? Is there a way to duplicate a
> database at the file system level and them update the DBMS system
> tables (or whatever) so the new files are recognized properly.
> TIA.
> Yours - Billy
> ============================================================> William Goedicke goedicke@.goedsole.com
> http://www.goedsole.com:8080
> ============================================================> Lest we forget:
> Don't force it; get a bigger hammer.
> - Al Dodge|||When you do the restores you will need to specify new paths for the data nd
lof files as well. You can do this in Enterprise Manager or use the WITH
MOVE option in Query Analyzer.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||In my last post it should have been:
When you do the restores you will need to specify new paths for the data
and
log files as well. You can do this in Enterprise Manager or use the WITH
MOVE option in Query Analyzer.
This posting is provided "as is" with no warranties and confers no rights.|||If you use EM for the restore, the filenames get changed wrt the new name
automatically, at least in my experience.
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Rand Boyd [MS]" <rboyd@.onlinemicrosoft.com> wrote in message
news:rD7WE2KxDHA.3660@.cpmsftngxa07.phx.gbl...
> When you do the restores you will need to specify new paths for the data
nd
> lof files as well. You can do this in Enterprise Manager or use the WITH
> MOVE option in Query Analyzer.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>

Friday, February 17, 2012

Copy subscription fails

I understand that there is a limitation in windows for compressing 2gb +. I
am trying to create an msf by "copying a subscription". As an alternative
method I have tried to copy the subscription database using the "copy
database" wizard it gives me an error that is supposedly suppost to be a
permissions problem. Has anyone in the group been able to figure out where
the permissions are to be set to copy a database between two servers. I've
already tried the domain administrator in which both machines are members
of.
there error you are probably getting is because an account or dbuser is not
present in the target database.
repeat the copy and post back here with the exact error message you are
getting.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Sam" <sam@.info.com> wrote in message
news:10f89dua28ama86@.corp.supernews.com...
> I understand that there is a limitation in windows for compressing 2gb +.
I
> am trying to create an msf by "copying a subscription". As an alternative
> method I have tried to copy the subscription database using the "copy
> database" wizard it gives me an error that is supposedly suppost to be a
> permissions problem. Has anyone in the group been able to figure out where
> the permissions are to be set to copy a database between two servers.
I've
> already tried the domain administrator in which both machines are members
> of.
>
|||I figured out how to copy a database. Thank you for your help. But the
original issue was to avoid using the copy subscription method which is
limited to 2gb. The copy database wizard does not allow me to copy a
replication database. How do I get a subscription on another machine without
using snapshot folders. I loved the msf files because you can manage it
easily with novice users but like I said before it has a 2gb limit. What is
the simplest way to move the subscriptions without a snapshot folder (merge
replication)?
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:uIpE6MRaEHA.3112@.tk2msftngp13.phx.gbl...
> there error you are probably getting is because an account or dbuser is
not[vbcol=seagreen]
> present in the target database.
> repeat the copy and post back here with the exact error message you are
> getting.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Sam" <sam@.info.com> wrote in message
> news:10f89dua28ama86@.corp.supernews.com...
+.[vbcol=seagreen]
> I
alternative[vbcol=seagreen]
where[vbcol=seagreen]
> I've
members
>
|||back up the publication database, copy the backup file to the subscriber and
restore it there. Then do a nosync subscribption.
A small snapshot will be generated and distributed to your subscription with
procs, triggers, and metadata merge needs to work.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Sam" <sam@.info.com> wrote in message
news:10faqndd1576a3d@.corp.supernews.com...
> I figured out how to copy a database. Thank you for your help. But the
> original issue was to avoid using the copy subscription method which is
> limited to 2gb. The copy database wizard does not allow me to copy a
> replication database. How do I get a subscription on another machine
without
> using snapshot folders. I loved the msf files because you can manage it
> easily with novice users but like I said before it has a 2gb limit. What
is
> the simplest way to move the subscriptions without a snapshot folder
(merge[vbcol=seagreen]
> replication)?
> "Hilary Cotter" <hilaryk@.att.net> wrote in message
> news:uIpE6MRaEHA.3112@.tk2msftngp13.phx.gbl...
> not
> +.
> alternative
a[vbcol=seagreen]
> where

> members
>
|||I tried what you've told me and it worked great so far. However nothing is
too simple I got the following message:
The merge process could not initialize the subscription.
{?=call sp_MSaddanonymousreplica (?,?,?,?,?,?)}
Invalid subscription type is specified. A subscription to publication 'XXX'
already exists in the database with a different subscription
I tried to drop the subscription but said it doesn't exist
sp_droppullsubscription
@.publisher='BUSHWACKER\TEST',@.publisher_db='XXX',
@.publication='XXX'
Server: Msg 14135, Level 11, State 1, Procedure sp_droppullsubscription,
Line 143
There is no subscription on Publisher 'BUSHWACKER\TEST', publisher database
'XXX', publication 'XXX'.
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:uH#hwylaEHA.3692@.TK2MSFTNGP09.phx.gbl...
> back up the publication database, copy the backup file to the subscriber
and
> restore it there. Then do a nosync subscribption.
> A small snapshot will be generated and distributed to your subscription
with[vbcol=seagreen]
> procs, triggers, and metadata merge needs to work.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Sam" <sam@.info.com> wrote in message
> news:10faqndd1576a3d@.corp.supernews.com...
> without
> is
> (merge
is[vbcol=seagreen]
are[vbcol=seagreen]
2gb[vbcol=seagreen]
"copy[vbcol=seagreen]
be[vbcol=seagreen]
> a
servers.
>
>

Tuesday, March 27, 2012

Correct Memory Configuration for 4GB/W2K3 Enterprise

Correct Memory Configuration for 4GB/W2K3 Enterprise

Correct Memory Configuration for 4GB/W2K3 Enterprise

Sunday, March 11, 2012

Copying database to new name on same server

Friday, February 17, 2012

Copy subscription fails

sql server db

Blog Archive

About Me