Backing up and restoring SQL Server

I want to reformat my servers harddrive and install a newer operating
system (Win 2003). I am running SQL Server 2000 with about 10
databases. What is the best way to backup and restore SQL Server for
this so I don't lose anything.
Thanks,
RickRick (rick@.abasoftware.com) writes:
> I want to reformat my servers harddrive and install a newer operating
> system (Win 2003). I am running SQL Server 2000 with about 10
> databases. What is the best way to backup and restore SQL Server for
> this so I don't lose anything.

Look at http://support.microsoft.com/defaul...kb;EN-US;224071.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

AWE Memory: Seeing approx. 1 Gig less than expected

I am runnning a dedicated SQL Server 2005 Standard edition server on Win 200
3,
with 16 GB RAM.
I have AWE enabled, with a Max Server Memory of 14336 (14 GB).
I have /3GB /PAE set in the boot.ini.
When I run SQLServer:Memory Manager, Target Memory (KB) in Perfmon, I only
see 13722592 KB (or 13400.96875 MB, 13.086 GB) being used out of the 14 GB
specified.
Is this normal, or am I being robbed of a Gig of memory somewhere?
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200610/1If I recall correctly, AWE consumes about 1GB of memory as overhead.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:67a8999d3983c@.uwe...
>I am runnning a dedicated SQL Server 2005 Standard edition server on Win
>2003,
> with 16 GB RAM.
> I have AWE enabled, with a Max Server Memory of 14336 (14 GB).
> I have /3GB /PAE set in the boot.ini.
> When I run SQLServer:Memory Manager, Target Memory (KB) in Perfmon, I only
> see 13722592 KB (or 13400.96875 MB, 13.086 GB) being used out of the 14 GB
> specified.
> Is this normal, or am I being robbed of a Gig of memory somewhere?
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200610/1
>|||Thanks Arnie. I do not dispute that, but it does make me scratch my head.
On another dedicated SQL Server, identical to the current one I am building,
except this other one has only 8 GB of RAM, when I set the Max Server Memory
to 6144 (6 GB), I see all 6144 in Target Memory. If SQL Server keeps 1 GB to
itself, then I would expect to only see 5 GB being used in Target Memory, bu
t
no, I am seeing all 6 GB on my 8 GB machine. Just makes me wonder...makes me
feel like I am being cheated out of approximately 1 GB on my 16 GB server,
since I have 14 GB specified in Max Server Memory and am only seeing 13 GB i
n
Target Memory.
Arnie Rowland wrote:[vbcol=seagreen]
>If I recall correctly, AWE consumes about 1GB of memory as overhead.
>
>[quoted text clipped - 9 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200610/1|||I really don't recall if that 1GB overhead is in addition to the AWE
allocation, or if it is part of the AWE allocation. (I always thought that
it was outside of the AWE allocation.)
So, back to your situation.
Is it possible that there is some other usage on the box that is grabbing
memory from the OS before AWE can get it's share (thereby leaving only 13GB
for AWE)?
Another instance of SQL Server with /3GB switch?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:67a9b4e454ccc@.uwe...
> Thanks Arnie. I do not dispute that, but it does make me scratch my head.
> On another dedicated SQL Server, identical to the current one I am
> building,
> except this other one has only 8 GB of RAM, when I set the Max Server
> Memory
> to 6144 (6 GB), I see all 6144 in Target Memory. If SQL Server keeps 1 GB
> to
> itself, then I would expect to only see 5 GB being used in Target Memory,
> but
> no, I am seeing all 6 GB on my 8 GB machine. Just makes me wonder...makes
> me
> feel like I am being cheated out of approximately 1 GB on my 16 GB server,
> since I have 14 GB specified in Max Server Memory and am only seeing 13 GB
> in
> Target Memory.
> Arnie Rowland wrote:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200610/1
>|||I suspect that is the case (some other usage on the box is grabbing memory),
but it is not another instance. I am still investigating.
Arnie Rowland wrote:[vbcol=seagreen]
>I really don't recall if that 1GB overhead is in addition to the AWE
>allocation, or if it is part of the AWE allocation. (I always thought that
>it was outside of the AWE allocation.)
>So, back to your situation.
>Is it possible that there is some other usage on the box that is grabbing
>memory from the OS before AWE can get it's share (thereby leaving only 13GB
>for AWE)?
>Another instance of SQL Server with /3GB switch?
>
>[quoted text clipped - 20 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200610/1

AWE Memory: Seeing approx. 1 Gig less than expected

I am runnning a dedicated SQL Server 2005 Standard edition server on Win 2003,
with 16 GB RAM.
I have AWE enabled, with a Max Server Memory of 14336 (14 GB).
I have /3GB /PAE set in the boot.ini.
When I run SQLServer:Memory Manager, Target Memory (KB) in Perfmon, I only
see 13722592 KB (or 13400.96875 MB, 13.086 GB) being used out of the 14 GB
specified.
Is this normal, or am I being robbed of a Gig of memory somewhere?
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200610/1
If I recall correctly, AWE consumes about 1GB of memory as overhead.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:67a8999d3983c@.uwe...
>I am runnning a dedicated SQL Server 2005 Standard edition server on Win
>2003,
> with 16 GB RAM.
> I have AWE enabled, with a Max Server Memory of 14336 (14 GB).
> I have /3GB /PAE set in the boot.ini.
> When I run SQLServer:Memory Manager, Target Memory (KB) in Perfmon, I only
> see 13722592 KB (or 13400.96875 MB, 13.086 GB) being used out of the 14 GB
> specified.
> Is this normal, or am I being robbed of a Gig of memory somewhere?
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200610/1
>
|||Thanks Arnie. I do not dispute that, but it does make me scratch my head.
On another dedicated SQL Server, identical to the current one I am building,
except this other one has only 8 GB of RAM, when I set the Max Server Memory
to 6144 (6 GB), I see all 6144 in Target Memory. If SQL Server keeps 1 GB to
itself, then I would expect to only see 5 GB being used in Target Memory, but
no, I am seeing all 6 GB on my 8 GB machine. Just makes me wonder...makes me
feel like I am being cheated out of approximately 1 GB on my 16 GB server,
since I have 14 GB specified in Max Server Memory and am only seeing 13 GB in
Target Memory.
Arnie Rowland wrote:[vbcol=seagreen]
>If I recall correctly, AWE consumes about 1GB of memory as overhead.
>[quoted text clipped - 9 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200610/1
|||I really don't recall if that 1GB overhead is in addition to the AWE
allocation, or if it is part of the AWE allocation. (I always thought that
it was outside of the AWE allocation.)
So, back to your situation.
Is it possible that there is some other usage on the box that is grabbing
memory from the OS before AWE can get it's share (thereby leaving only 13GB
for AWE)?
Another instance of SQL Server with /3GB switch?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:67a9b4e454ccc@.uwe...
> Thanks Arnie. I do not dispute that, but it does make me scratch my head.
> On another dedicated SQL Server, identical to the current one I am
> building,
> except this other one has only 8 GB of RAM, when I set the Max Server
> Memory
> to 6144 (6 GB), I see all 6144 in Target Memory. If SQL Server keeps 1 GB
> to
> itself, then I would expect to only see 5 GB being used in Target Memory,
> but
> no, I am seeing all 6 GB on my 8 GB machine. Just makes me wonder...makes
> me
> feel like I am being cheated out of approximately 1 GB on my 16 GB server,
> since I have 14 GB specified in Max Server Memory and am only seeing 13 GB
> in
> Target Memory.
> Arnie Rowland wrote:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200610/1
>
|||I suspect that is the case (some other usage on the box is grabbing memory),
but it is not another instance. I am still investigating.
Arnie Rowland wrote:[vbcol=seagreen]
>I really don't recall if that 1GB overhead is in addition to the AWE
>allocation, or if it is part of the AWE allocation. (I always thought that
>it was outside of the AWE allocation.)
>So, back to your situation.
>Is it possible that there is some other usage on the box that is grabbing
>memory from the OS before AWE can get it's share (thereby leaving only 13GB
>for AWE)?
>Another instance of SQL Server with /3GB switch?
>[quoted text clipped - 20 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200610/1

AWE Memory: Seeing approx. 1 Gig less than expected

I am runnning a dedicated SQL Server 2005 Standard edition server on Win 2003,
with 16 GB RAM.
I have AWE enabled, with a Max Server Memory of 14336 (14 GB).
I have /3GB /PAE set in the boot.ini.
When I run SQLServer:Memory Manager, Target Memory (KB) in Perfmon, I only
see 13722592 KB (or 13400.96875 MB, 13.086 GB) being used out of the 14 GB
specified.
Is this normal, or am I being robbed of a Gig of memory somewhere?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200610/1If I recall correctly, AWE consumes about 1GB of memory as overhead.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"cbrichards via SQLMonster.com" <u3288@.uwe> wrote in message
news:67a8999d3983c@.uwe...
>I am runnning a dedicated SQL Server 2005 Standard edition server on Win
>2003,
> with 16 GB RAM.
> I have AWE enabled, with a Max Server Memory of 14336 (14 GB).
> I have /3GB /PAE set in the boot.ini.
> When I run SQLServer:Memory Manager, Target Memory (KB) in Perfmon, I only
> see 13722592 KB (or 13400.96875 MB, 13.086 GB) being used out of the 14 GB
> specified.
> Is this normal, or am I being robbed of a Gig of memory somewhere?
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200610/1
>|||Thanks Arnie. I do not dispute that, but it does make me scratch my head.
On another dedicated SQL Server, identical to the current one I am building,
except this other one has only 8 GB of RAM, when I set the Max Server Memory
to 6144 (6 GB), I see all 6144 in Target Memory. If SQL Server keeps 1 GB to
itself, then I would expect to only see 5 GB being used in Target Memory, but
no, I am seeing all 6 GB on my 8 GB machine. Just makes me wonder...makes me
feel like I am being cheated out of approximately 1 GB on my 16 GB server,
since I have 14 GB specified in Max Server Memory and am only seeing 13 GB in
Target Memory.
Arnie Rowland wrote:
>If I recall correctly, AWE consumes about 1GB of memory as overhead.
>>I am runnning a dedicated SQL Server 2005 Standard edition server on Win
>>2003,
>[quoted text clipped - 9 lines]
>> Is this normal, or am I being robbed of a Gig of memory somewhere?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200610/1|||I really don't recall if that 1GB overhead is in addition to the AWE
allocation, or if it is part of the AWE allocation. (I always thought that
it was outside of the AWE allocation.)
So, back to your situation.
Is it possible that there is some other usage on the box that is grabbing
memory from the OS before AWE can get it's share (thereby leaving only 13GB
for AWE)?
Another instance of SQL Server with /3GB switch?
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"cbrichards via SQLMonster.com" <u3288@.uwe> wrote in message
news:67a9b4e454ccc@.uwe...
> Thanks Arnie. I do not dispute that, but it does make me scratch my head.
> On another dedicated SQL Server, identical to the current one I am
> building,
> except this other one has only 8 GB of RAM, when I set the Max Server
> Memory
> to 6144 (6 GB), I see all 6144 in Target Memory. If SQL Server keeps 1 GB
> to
> itself, then I would expect to only see 5 GB being used in Target Memory,
> but
> no, I am seeing all 6 GB on my 8 GB machine. Just makes me wonder...makes
> me
> feel like I am being cheated out of approximately 1 GB on my 16 GB server,
> since I have 14 GB specified in Max Server Memory and am only seeing 13 GB
> in
> Target Memory.
> Arnie Rowland wrote:
>>If I recall correctly, AWE consumes about 1GB of memory as overhead.
>>I am runnning a dedicated SQL Server 2005 Standard edition server on Win
>>2003,
>>[quoted text clipped - 9 lines]
>> Is this normal, or am I being robbed of a Gig of memory somewhere?
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200610/1
>|||I suspect that is the case (some other usage on the box is grabbing memory),
but it is not another instance. I am still investigating.
Arnie Rowland wrote:
>I really don't recall if that 1GB overhead is in addition to the AWE
>allocation, or if it is part of the AWE allocation. (I always thought that
>it was outside of the AWE allocation.)
>So, back to your situation.
>Is it possible that there is some other usage on the box that is grabbing
>memory from the OS before AWE can get it's share (thereby leaving only 13GB
>for AWE)?
>Another instance of SQL Server with /3GB switch?
>> Thanks Arnie. I do not dispute that, but it does make me scratch my head.
>[quoted text clipped - 20 lines]
>> Is this normal, or am I being robbed of a Gig of memory somewhere?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200610/1

AWE and SQL 2000

Win 2000 server, SQL 2000

What exactly does the /3GB do?

We have added 4GB of RAM to an existing 4, but have not yet added the switch, although /PAE has been in the boot.ini file for some time. (why would that be? THat switch is for the os, isn't it? Does win 2000 not handle the 4GB of RAM?)

In my research, it says that SQL Server will only be able to access 2GB of memory without it, however, there is 4GB on the server now, so won't it continue to use the 4? SHould the switch be different?

Should the switch ever be different? Once you get to 36GB aren't you supposed to leave the switch off, and why?

We are going to upgrade to Win 2003 - is there anything different we will need to do in order to use the full 8GB? It is not planned to enable AWE until we go to Win 2003, although I can't get an answer on why that would be from our server people - is there a known issue on upgrade?

/3GB allows Windows applications that are marked LargeAddressAware (which SS 2000 is) to have 3GB of user virtual address space instead of the usual 2GB. For SQL Server, this is usually a good idea because it greatly reduces problems related to address space management in 32-bits.

If you do not have AWE enabled, the size of the user virtual address space also forms an upper limit on how much physical memory SQL Server can use; if AWE is enabled, then SQL Server can use up to 64GB of physical memory, but still within the confines of either a 2GB or 3GB address space.

I'm not sure why one would only enable AWE for SS 2000 on Win 2003 and not Win 2000. The amount of physical memory used would be fixed in size, and allocated at server startup. Things are different for SS 2005, but that's another story.

AWE and Perfmon Counters

We have enabled AWE on our SQL 2000/Win 2003 Ent servers and are now having
problems seeing true memory utilization by SQL Server. For example, Task
Manager shows SQL only using 174,712 k when it has been configured to 13gb.
Not to mention perfmon memory object is not reporting accurately either.
With that said, is this a known issue and what is the work around? I want
to be able to guage if we need more than 16gb on this box.
Thanks!
MichaelTask manager cannot count higher than 2GB of memory. The performance
monitor counters will give accurate memory usage. Another quick and dirty
way is to look at Page File usage. AWE usage shows up as page file
committment.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"BATMAN" <BATMAN@.discussions.microsoft.com> wrote in message
news:48B6C39B-8DB3-4B20-B487-935ADF37D952@.microsoft.com...
> We have enabled AWE on our SQL 2000/Win 2003 Ent servers and are now
> having
> problems seeing true memory utilization by SQL Server. For example, Task
> Manager shows SQL only using 174,712 k when it has been configured to
> 13gb.
> Not to mention perfmon memory object is not reporting accurately either.
> With that said, is this a known issue and what is the work around? I want
> to be able to guage if we need more than 16gb on this box.
> Thanks!
> Michael
>

AWE and Perfmon Counters

We have enabled AWE on our SQL 2000/Win 2003 Ent servers and are now having
problems seeing true memory utilization by SQL Server. For example, Task
Manager shows SQL only using 174,712 k when it has been configured to 13gb.
Not to mention perfmon memory object is not reporting accurately either.
With that said, is this a known issue and what is the work around? I want
to be able to guage if we need more than 16gb on this box.
Thanks!
Michael
Task manager cannot count higher than 2GB of memory. The performance
monitor counters will give accurate memory usage. Another quick and dirty
way is to look at Page File usage. AWE usage shows up as page file
committment.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"BATMAN" <BATMAN@.discussions.microsoft.com> wrote in message
news:48B6C39B-8DB3-4B20-B487-935ADF37D952@.microsoft.com...
> We have enabled AWE on our SQL 2000/Win 2003 Ent servers and are now
> having
> problems seeing true memory utilization by SQL Server. For example, Task
> Manager shows SQL only using 174,712 k when it has been configured to
> 13gb.
> Not to mention perfmon memory object is not reporting accurately either.
> With that said, is this a known issue and what is the work around? I want
> to be able to guage if we need more than 16gb on this box.
> Thanks!
> Michael
>

AWE + PAE + 3GB cause system to freeze?

Hi,
I have a server with 8Gb of memory
so the /3Gb and /PAE switches are in the boot.ini.
I'm using Win 2003 Ent. & SQL 2000 ent.
at regular basis, my system freeze for some seconds if the AWE option is on.
any idea of what's appends?
My server also host Analysis Services + IIS + Sharepoint + Reporting
Services.
thanks.
Jerome."Jéjé" <willgart@.BBBhotmailAAA.com> wrote in message
news:ecI4P2S0FHA.3000@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I have a server with 8Gb of memory
> so the /3Gb and /PAE switches are in the boot.ini.
> I'm using Win 2003 Ent. & SQL 2000 ent.
> at regular basis, my system freeze for some seconds if the AWE option is
> on.
> any idea of what's appends?
> My server also host Analysis Services + IIS + Sharepoint + Reporting
> Services.
>
It's not generally recommended to use AWE if the server is not dedicated to
SQL Server. Leave the /3GB switch, but get rid of /PAE and AWE. Give 3GB
to SQL Server and leave 2G for Analysis Services, and 2G for IIS, Sharepoint
and Reporting.
David|||in this configuration, only 4Gb is used by the applications
AS consumme 200mb, 200mb for sharepoint & RS
SQL use 2.7 Gb
So I have a lot of free memory.
But also... for the moment I'm in dev mode, and only SQL Server is used, so
the other applications don't use any ressources and are in standby.
I'm just using DTS to load data in my databases.
"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:uFjaGMT0FHA.1028@.TK2MSFTNGP12.phx.gbl...
> "Jéjé" <willgart@.BBBhotmailAAA.com> wrote in message
> news:ecI4P2S0FHA.3000@.TK2MSFTNGP12.phx.gbl...
>> Hi,
>> I have a server with 8Gb of memory
>> so the /3Gb and /PAE switches are in the boot.ini.
>> I'm using Win 2003 Ent. & SQL 2000 ent.
>> at regular basis, my system freeze for some seconds if the AWE option is
>> on.
>> any idea of what's appends?
>> My server also host Analysis Services + IIS + Sharepoint + Reporting
>> Services.
> It's not generally recommended to use AWE if the server is not dedicated
> to SQL Server. Leave the /3GB switch, but get rid of /PAE and AWE. Give
> 3GB to SQL Server and leave 2G for Analysis Services, and 2G for IIS,
> Sharepoint and Reporting.
> David
>