Showing posts with label cause. Show all posts
Showing posts with label cause. Show all posts

Thursday, March 22, 2012

Backing up a primary log shipping database

Hi,
Does backing up a primary database in a log shipping pair cause problem in
the log shipping?
Aside from an on-going log shipping maintenance between a Primary &
Secondary (latency 15 minutes) database, I would like to schedule a daily
complete backup of the primary database and an hourly transaction log backup
.
I already tested this and so far log shipping continued but I just want to
confirm if this has no lurking issues. AFAIK, transaction log backup
truncates the log files that is why I am wondering how can the other
transaction log backup the log files if it is already truncated.
Your comments will be highly appreciated.
--
...A database backup does *not* break the sequence of log backups. I.e., it is
safe to do database
backups of a log shipped database.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"CarloVino" <CarloVino@.discussions.microsoft.com> wrote in message
news:714B75B2-AA8C-46FF-8B1F-A1B6B348F2CA@.microsoft.com...
> Hi,
> Does backing up a primary database in a log shipping pair cause problem in
> the log shipping?
> Aside from an on-going log shipping maintenance between a Primary &
> Secondary (latency 15 minutes) database, I would like to schedule a daily
> complete backup of the primary database and an hourly transaction log back
up.
> I already tested this and so far log shipping continued but I just want
to
> confirm if this has no lurking issues. AFAIK, transaction log backup
> truncates the log files that is why I am wondering how can the other
> transaction log backup the log files if it is already truncated.
> Your comments will be highly appreciated.
> --
> ...|||But what about transaction log backups? Does xp_sqlmaint (when it's
doing the copy phase on the secondary server) look up the msdb.backupset
& msdb.backupmediafamily tables on the primary server to get the
location of the physical log backup files (even the ones done by
processes other than the logshipping plan's xp_sqlmaint call, like
another maint plan or ad-hoc tlog backups)? Or does it just pick up log
backup files from a certain directory or created by the xp_sqlmaint
backup phase on the primary?
If it's the later then ad-hoc log backups, or log backups done by
another maint plan, would disrupt the logshipping sync (and in fact the
log shipping tlog backups would make the log backups done by the other
maint plan out of sequence).
On the whole, having 2 different plans (one log shipping plan and one
other maint plan) doing transaction log backups just sounds like a bad
idea (and redundant anyway). Why have another plan doing hourly tlog
backups when the logshipping plan is doing them every 15 minutes anyway?
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Tibor Karaszi wrote:

>A database backup does *not* break the sequence of log backups. I.e., it is
safe to do database
>backups of a log shipped database.
>
>|||I don't use xp_sqlmaint for log shipping. But I'd be very surprise if it wou
ld pick up out-of-band
backups. My point was that out-of-band *database* backup doesn't disrupt log
shipping. Out-of-band
log backups does. I was under the impression that the OP was asking about da
tabase backup, so thanks
for pushing the point, Mike. :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message
news:ONlx0j4zFHA.1192@.TK2MSFTNGP10.phx.gbl...
> But what about transaction log backups? Does xp_sqlmaint (when it's
> doing the copy phase on the secondary server) look up the msdb.backupset
> & msdb.backupmediafamily tables on the primary server to get the
> location of the physical log backup files (even the ones done by
> processes other than the logshipping plan's xp_sqlmaint call, like
> another maint plan or ad-hoc tlog backups)? Or does it just pick up log
> backup files from a certain directory or created by the xp_sqlmaint
> backup phase on the primary?
> If it's the later then ad-hoc log backups, or log backups done by
> another maint plan, would disrupt the logshipping sync (and in fact the
> log shipping tlog backups would make the log backups done by the other
> maint plan out of sequence).
> On the whole, having 2 different plans (one log shipping plan and one
> other maint plan) doing transaction log backups just sounds like a bad
> idea (and redundant anyway). Why have another plan doing hourly tlog
> backups when the logshipping plan is doing them every 15 minutes anyway?
> --
> *mike hodgson*
> blog: http://sqlnerd.blogspot.com
>
> Tibor Karaszi wrote:
>
>|||How do you implement log shipping if you don't use xp_sqlmaint (as
that's what the DB Maintenance Wizard uses when it creates all the
SQLAgent jobs)? Have you implemented your own home-grown log shipping
solution?
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Tibor Karaszi wrote:

>I don't use xp_sqlmaint for log shipping. But I'd be very surprise if it wo
uld pick up out-of-band
>backups. My point was that out-of-band *database* backup doesn't disrupt lo
g shipping. Out-of-band
>log backups does. I was under the impression that the OP was asking about d
atabase backup, so thanks
>for pushing the point, Mike. :-)
>
>|||> Have you implemented your own home-grown log shipping
> solution?
Yep. I'm using www.dbmaint.com (since I write part of it, and while implemen
ting test-restore I
realized it was pretty much same thing as implementing log shipping), but lo
ts of people here also
just use their own jobs (I'm, pretty certain some has been posted here).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message
news:uayUtD8zFHA.1168@.TK2MSFTNGP10.phx.gbl...
> How do you implement log shipping if you don't use xp_sqlmaint (as
> that's what the DB Maintenance Wizard uses when it creates all the
> SQLAgent jobs)? Have you implemented your own home-grown log shipping
> solution?
> --
> *mike hodgson*
> blog: http://sqlnerd.blogspot.com
>
> Tibor Karaszi wrote:
>
>sql

Backing up a primary log shipping database

Hi,
Does backing up a primary database in a log shipping pair cause problem in
the log shipping?
Aside from an on-going log shipping maintenance between a Primary &
Secondary (latency 15 minutes) database, I would like to schedule a daily
complete backup of the primary database and an hourly transaction log backup.
I already tested this and so far log shipping continued but I just want to
confirm if this has no lurking issues. AFAIK, transaction log backup
truncates the log files that is why I am wondering how can the other
transaction log backup the log files if it is already truncated.
Your comments will be highly appreciated.
...
A database backup does *not* break the sequence of log backups. I.e., it is safe to do database
backups of a log shipped database.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"CarloVino" <CarloVino@.discussions.microsoft.com> wrote in message
news:714B75B2-AA8C-46FF-8B1F-A1B6B348F2CA@.microsoft.com...
> Hi,
> Does backing up a primary database in a log shipping pair cause problem in
> the log shipping?
> Aside from an on-going log shipping maintenance between a Primary &
> Secondary (latency 15 minutes) database, I would like to schedule a daily
> complete backup of the primary database and an hourly transaction log backup.
> I already tested this and so far log shipping continued but I just want to
> confirm if this has no lurking issues. AFAIK, transaction log backup
> truncates the log files that is why I am wondering how can the other
> transaction log backup the log files if it is already truncated.
> Your comments will be highly appreciated.
> --
> ...
|||But what about transaction log backups? Does xp_sqlmaint (when it's
doing the copy phase on the secondary server) look up the msdb.backupset
& msdb.backupmediafamily tables on the primary server to get the
location of the physical log backup files (even the ones done by
processes other than the logshipping plan's xp_sqlmaint call, like
another maint plan or ad-hoc tlog backups)? Or does it just pick up log
backup files from a certain directory or created by the xp_sqlmaint
backup phase on the primary?
If it's the later then ad-hoc log backups, or log backups done by
another maint plan, would disrupt the logshipping sync (and in fact the
log shipping tlog backups would make the log backups done by the other
maint plan out of sequence).
On the whole, having 2 different plans (one log shipping plan and one
other maint plan) doing transaction log backups just sounds like a bad
idea (and redundant anyway). Why have another plan doing hourly tlog
backups when the logshipping plan is doing them every 15 minutes anyway?
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Tibor Karaszi wrote:

>A database backup does *not* break the sequence of log backups. I.e., it is safe to do database
>backups of a log shipped database.
>
>
|||I don't use xp_sqlmaint for log shipping. But I'd be very surprise if it would pick up out-of-band
backups. My point was that out-of-band *database* backup doesn't disrupt log shipping. Out-of-band
log backups does. I was under the impression that the OP was asking about database backup, so thanks
for pushing the point, Mike. :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message
news:ONlx0j4zFHA.1192@.TK2MSFTNGP10.phx.gbl...
> But what about transaction log backups? Does xp_sqlmaint (when it's
> doing the copy phase on the secondary server) look up the msdb.backupset
> & msdb.backupmediafamily tables on the primary server to get the
> location of the physical log backup files (even the ones done by
> processes other than the logshipping plan's xp_sqlmaint call, like
> another maint plan or ad-hoc tlog backups)? Or does it just pick up log
> backup files from a certain directory or created by the xp_sqlmaint
> backup phase on the primary?
> If it's the later then ad-hoc log backups, or log backups done by
> another maint plan, would disrupt the logshipping sync (and in fact the
> log shipping tlog backups would make the log backups done by the other
> maint plan out of sequence).
> On the whole, having 2 different plans (one log shipping plan and one
> other maint plan) doing transaction log backups just sounds like a bad
> idea (and redundant anyway). Why have another plan doing hourly tlog
> backups when the logshipping plan is doing them every 15 minutes anyway?
> --
> *mike hodgson*
> blog: http://sqlnerd.blogspot.com
>
> Tibor Karaszi wrote:
>
|||How do you implement log shipping if you don't use xp_sqlmaint (as
that's what the DB Maintenance Wizard uses when it creates all the
SQLAgent jobs)? Have you implemented your own home-grown log shipping
solution?
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Tibor Karaszi wrote:

>I don't use xp_sqlmaint for log shipping. But I'd be very surprise if it would pick up out-of-band
>backups. My point was that out-of-band *database* backup doesn't disrupt log shipping. Out-of-band
>log backups does. I was under the impression that the OP was asking about database backup, so thanks
>for pushing the point, Mike. :-)
>
>
|||> Have you implemented your own home-grown log shipping
> solution?
Yep. I'm using www.dbmaint.com (since I write part of it, and while implementing test-restore I
realized it was pretty much same thing as implementing log shipping), but lots of people here also
just use their own jobs (I'm, pretty certain some has been posted here).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message
news:uayUtD8zFHA.1168@.TK2MSFTNGP10.phx.gbl...
> How do you implement log shipping if you don't use xp_sqlmaint (as
> that's what the DB Maintenance Wizard uses when it creates all the
> SQLAgent jobs)? Have you implemented your own home-grown log shipping
> solution?
> --
> *mike hodgson*
> blog: http://sqlnerd.blogspot.com
>
> Tibor Karaszi wrote:
>

Backing up a primary log shipping database

Hi,
Does backing up a primary database in a log shipping pair cause problem in
the log shipping?
Aside from an on-going log shipping maintenance between a Primary &
Secondary (latency 15 minutes) database, I would like to schedule a daily
complete backup of the primary database and an hourly transaction log backup.
I already tested this and so far log shipping continued but I just want to
confirm if this has no lurking issues. AFAIK, transaction log backup
truncates the log files that is why I am wondering how can the other
transaction log backup the log files if it is already truncated.
Your comments will be highly appreciated.
--
...A database backup does *not* break the sequence of log backups. I.e., it is safe to do database
backups of a log shipped database.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"CarloVino" <CarloVino@.discussions.microsoft.com> wrote in message
news:714B75B2-AA8C-46FF-8B1F-A1B6B348F2CA@.microsoft.com...
> Hi,
> Does backing up a primary database in a log shipping pair cause problem in
> the log shipping?
> Aside from an on-going log shipping maintenance between a Primary &
> Secondary (latency 15 minutes) database, I would like to schedule a daily
> complete backup of the primary database and an hourly transaction log backup.
> I already tested this and so far log shipping continued but I just want to
> confirm if this has no lurking issues. AFAIK, transaction log backup
> truncates the log files that is why I am wondering how can the other
> transaction log backup the log files if it is already truncated.
> Your comments will be highly appreciated.
> --
> ...|||This is a multi-part message in MIME format.
--010003020805070908090803
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
But what about transaction log backups? Does xp_sqlmaint (when it's
doing the copy phase on the secondary server) look up the msdb.backupset
& msdb.backupmediafamily tables on the primary server to get the
location of the physical log backup files (even the ones done by
processes other than the logshipping plan's xp_sqlmaint call, like
another maint plan or ad-hoc tlog backups)? Or does it just pick up log
backup files from a certain directory or created by the xp_sqlmaint
backup phase on the primary?
If it's the later then ad-hoc log backups, or log backups done by
another maint plan, would disrupt the logshipping sync (and in fact the
log shipping tlog backups would make the log backups done by the other
maint plan out of sequence).
On the whole, having 2 different plans (one log shipping plan and one
other maint plan) doing transaction log backups just sounds like a bad
idea (and redundant anyway). Why have another plan doing hourly tlog
backups when the logshipping plan is doing them every 15 minutes anyway?
--
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Tibor Karaszi wrote:
>A database backup does *not* break the sequence of log backups. I.e., it is safe to do database
>backups of a log shipped database.
>
>
--010003020805070908090803
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>But what about transaction log backups? Does xp_sqlmaint (when
it's doing the copy phase on the secondary server) look up the
msdb.backupset & msdb.backupmediafamily tables on the primary
server to get the location of the physical log backup files (even the
ones done by processes other than the logshipping plan's xp_sqlmaint
call, like another maint plan or ad-hoc tlog backups)? Or does it just
pick up log backup files from a certain directory or created by the
xp_sqlmaint backup phase on the primary?<br>
<br>
If it's the later then ad-hoc log backups, or log backups done by
another maint plan, would disrupt the logshipping sync (and in fact the
log shipping tlog backups would make the log backups done by the other
maint plan out of sequence).<br>
<br>
On the whole, having 2 different plans (one log shipping plan and one
other maint plan) doing transaction log backups just sounds like a bad
idea (and redundant anyway). Why have another plan doing hourly tlog
backups when the logshipping plan is doing them every 15 minutes anyway?<br>
</tt>
<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"><br>
<font face="Tahoma" size="2">blog:</font><font face="Tahoma" size="2"> <a
href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
Tibor Karaszi wrote:
<blockquote cite="mideqP33exzFHA.3312@.TK2MSFTNGP09.phx.gbl" type="cite">
<pre wrap="">A database backup does *not* break the sequence of log backups. I.e., it is safe to do database
backups of a log shipped database.
</pre>
</blockquote>
</body>
</html>
--010003020805070908090803--|||I don't use xp_sqlmaint for log shipping. But I'd be very surprise if it would pick up out-of-band
backups. My point was that out-of-band *database* backup doesn't disrupt log shipping. Out-of-band
log backups does. I was under the impression that the OP was asking about database backup, so thanks
for pushing the point, Mike. :-)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message
news:ONlx0j4zFHA.1192@.TK2MSFTNGP10.phx.gbl...
> But what about transaction log backups? Does xp_sqlmaint (when it's
> doing the copy phase on the secondary server) look up the msdb.backupset
> & msdb.backupmediafamily tables on the primary server to get the
> location of the physical log backup files (even the ones done by
> processes other than the logshipping plan's xp_sqlmaint call, like
> another maint plan or ad-hoc tlog backups)? Or does it just pick up log
> backup files from a certain directory or created by the xp_sqlmaint
> backup phase on the primary?
> If it's the later then ad-hoc log backups, or log backups done by
> another maint plan, would disrupt the logshipping sync (and in fact the
> log shipping tlog backups would make the log backups done by the other
> maint plan out of sequence).
> On the whole, having 2 different plans (one log shipping plan and one
> other maint plan) doing transaction log backups just sounds like a bad
> idea (and redundant anyway). Why have another plan doing hourly tlog
> backups when the logshipping plan is doing them every 15 minutes anyway?
> --
> *mike hodgson*
> blog: http://sqlnerd.blogspot.com
>
> Tibor Karaszi wrote:
>>A database backup does *not* break the sequence of log backups. I.e., it is safe to do database
>>backups of a log shipped database.
>>
>|||This is a multi-part message in MIME format.
--050800090501060406070700
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
How do you implement log shipping if you don't use xp_sqlmaint (as
that's what the DB Maintenance Wizard uses when it creates all the
SQLAgent jobs)? Have you implemented your own home-grown log shipping
solution?
--
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Tibor Karaszi wrote:
>I don't use xp_sqlmaint for log shipping. But I'd be very surprise if it would pick up out-of-band
>backups. My point was that out-of-band *database* backup doesn't disrupt log shipping. Out-of-band
>log backups does. I was under the impression that the OP was asking about database backup, so thanks
>for pushing the point, Mike. :-)
>
>
--050800090501060406070700
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>How do you implement log shipping if you don't use xp_sqlmaint (as
that's what the DB Maintenance Wizard uses when it creates all the
SQLAgent jobs)? Have you implemented your own home-grown log shipping
solution?</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"><br>
<font face="Tahoma" size="2">blog:</font><font face="Tahoma" size="2"> <a
href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
Tibor Karaszi wrote:
<blockquote cite="mide9cjH47zFHA.3152@.TK2MSFTNGP10.phx.gbl" type="cite">
<pre wrap="">I don't use xp_sqlmaint for log shipping. But I'd be very surprise if it would pick up out-of-band
backups. My point was that out-of-band *database* backup doesn't disrupt log shipping. Out-of-band
log backups does. I was under the impression that the OP was asking about database backup, so thanks
for pushing the point, Mike. :-)
</pre>
</blockquote>
</body>
</html>
--050800090501060406070700--|||> Have you implemented your own home-grown log shipping
> solution?
Yep. I'm using www.dbmaint.com (since I write part of it, and while implementing test-restore I
realized it was pretty much same thing as implementing log shipping), but lots of people here also
just use their own jobs (I'm, pretty certain some has been posted here).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message
news:uayUtD8zFHA.1168@.TK2MSFTNGP10.phx.gbl...
> How do you implement log shipping if you don't use xp_sqlmaint (as
> that's what the DB Maintenance Wizard uses when it creates all the
> SQLAgent jobs)? Have you implemented your own home-grown log shipping
> solution?
> --
> *mike hodgson*
> blog: http://sqlnerd.blogspot.com
>
> Tibor Karaszi wrote:
>>I don't use xp_sqlmaint for log shipping. But I'd be very surprise if it would pick up out-of-band
>>backups. My point was that out-of-band *database* backup doesn't disrupt log shipping. Out-of-band
>>log backups does. I was under the impression that the OP was asking about database backup, so
>>thanks
>>for pushing the point, Mike. :-)
>>
>

Saturday, February 25, 2012

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
>

AWE /3GB performance

Is it possible to use AWE and /3gb option and cause the OS to become
constrained? Is so what key OS services are critical and which ones should
be stopped?
thank
-JohnJohn
If you have Windows 2000(Advanced or Datacenter) and 4GB RAM use /3GB (AWE
support isn't used)
You can provide more info to get more accurate advice
"John Grant" <JohnGrant@.discussions.microsoft.com> wrote in message
news:617A3083-DBEA-46C4-AFBE-C501839D12C7@.microsoft.com...
> Is it possible to use AWE and /3gb option and cause the OS to become
> constrained? Is so what key OS services are critical and which ones
> should
> be stopped?
> thank
> -John|||Hello John,
You can also use \PAE option if memory is more on the server e.g.8 GB and
SQL Server 2005 will manage the memory dynamically after the enabling the
AWE option.
Good Luck!
MB
"John Grant" <JohnGrant@.discussions.microsoft.com> wrote in message
news:617A3083-DBEA-46C4-AFBE-C501839D12C7@.microsoft.com...
> Is it possible to use AWE and /3gb option and cause the OS to become
> constrained? Is so what key OS services are critical and which ones
> should
> be stopped?
> thank
> -John|||John
>The /3GB switch is used to tell SQL Server to take advantage of 3GB out of
>the base 4GB of RAM that Windows 2000/3 supports natively. If you don't
>specify >this option, then SQL Server will only take advantage of 2GB of
>the first 4GB of RAM in the server, essentially wasting 1GB of RAM.
http://www.sql-server-performance.com/awe_memory.asp
"John Grant" <JohnGrant@.discussions.microsoft.com> wrote in message
news:A6CF4DB6-FFEE-4AA0-82B8-DD3BB04E6D74@.microsoft.com...
>I have 8gb of memory, win2003 server advanced, sql server 2000 ent. The
> concern when using the 3gb option is that I force the OS into 1gb of
> memory
> and causing the OS to be memory starved. Is it possible to create this
> condition and what would be the minimum set of services that should be
> running on the SQL Server box. For example, print spooler, application
> layer
> gateway, etc.
>
> "Uri Dimant" wrote:
>> John
>> If you have Windows 2000(Advanced or Datacenter) and 4GB RAM use /3GB
>> (AWE
>> support isn't used)
>> You can provide more info to get more accurate advice
>> "John Grant" <JohnGrant@.discussions.microsoft.com> wrote in message
>> news:617A3083-DBEA-46C4-AFBE-C501839D12C7@.microsoft.com...
>> > Is it possible to use AWE and /3gb option and cause the OS to become
>> > constrained? Is so what key OS services are critical and which ones
>> > should
>> > be stopped?
>> >
>> > thank
>> > -John
>>|||John
Is it SQL Server running dedicated on the server?
Do you have an OLTP applications connect to the SQL Server?
I'd strat to to identify perfomance problems from the application side (
checking indexes, database design)
"John Grant" <JohnGrant@.discussions.microsoft.com> wrote in message
news:DD6405A3-56C5-4394-81D5-121D204420F3@.microsoft.com...
> Uri, thanks for the info. I have read the doc and understand AWE and the
> 3gb
> option. Also I noticed some more advanced boot.ini options to control the
> use of the memory above 1g.
> I have a sql server that is running slow. I have not been able to profile
> the server. What I want to understand is "Is it possible to cause the OS
> to
> be memory starved using the 3gb option causing sql server to appear slow?"
> For example if the OS is forced to swap to disk for normal OS activities.
> If it is possible what would be the telling signs?
> thanks
> "Uri Dimant" wrote:
>> John
>> >The /3GB switch is used to tell SQL Server to take advantage of 3GB out
>> >of
>> >the base 4GB of RAM that Windows 2000/3 supports natively. If you don't
>> >specify >this option, then SQL Server will only take advantage of 2GB of
>> >the first 4GB of RAM in the server, essentially wasting 1GB of RAM.
>> http://www.sql-server-performance.com/awe_memory.asp
>>
>>
>> "John Grant" <JohnGrant@.discussions.microsoft.com> wrote in message
>> news:A6CF4DB6-FFEE-4AA0-82B8-DD3BB04E6D74@.microsoft.com...
>> >I have 8gb of memory, win2003 server advanced, sql server 2000 ent. The
>> > concern when using the 3gb option is that I force the OS into 1gb of
>> > memory
>> > and causing the OS to be memory starved. Is it possible to create this
>> > condition and what would be the minimum set of services that should be
>> > running on the SQL Server box. For example, print spooler, application
>> > layer
>> > gateway, etc.
>> >
>> >
>> > "Uri Dimant" wrote:
>> >
>> >> John
>> >>
>> >> If you have Windows 2000(Advanced or Datacenter) and 4GB RAM use
>> >> /3GB
>> >> (AWE
>> >> support isn't used)
>> >> You can provide more info to get more accurate advice
>> >>
>> >> "John Grant" <JohnGrant@.discussions.microsoft.com> wrote in message
>> >> news:617A3083-DBEA-46C4-AFBE-C501839D12C7@.microsoft.com...
>> >> > Is it possible to use AWE and /3gb option and cause the OS to become
>> >> > constrained? Is so what key OS services are critical and which ones
>> >> > should
>> >> > be stopped?
>> >> >
>> >> > thank
>> >> > -John
>> >>
>> >>
>> >>
>>