Autonumber field: installed

Showing posts with label installed. Show all posts

Thursday, March 29, 2012

Backing Up SQL Serv

I've installed MSDE SP3, and I'm looking for a script that runs once
before back-up to shut down the server, and once after backing-up, to
restart the server. This is supposed to go automatically. I'm running
Veritas Back_up Exec 9.0 (Without SQL extension... ).
Does anyone have an easy script for to run on my Win2k Server?
--
Jakob /n Powder (i.e. Snow) To The People
Posted via http://dbforums.comWhy do you want to shutdown the server, for creating a backup? The native
SQL Server BACKUP command is online and can backup databases that are
currently being accessed.
Are you trying to copy the physical files? If so, you may want to look at
NET STOP and NET START commands for stopping and starting services.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
What hardware is your SQL Server running on?
http://vyaskn.tripod.com/poll.htm
"JakobDi" <Jakob_di@.hotmail.com> wrote in message
news:3381077.1063810544@.dbforums.com...
I've installed MSDE SP3, and I'm looking for a script that runs once
before back-up to shut down the server, and once after backing-up, to
restart the server. This is supposed to go automatically. I'm running
Veritas Back_up Exec 9.0 (Without SQL extension... ).
Does anyone have an easy script for to run on my Win2k Server?
Jakob /n Powder (i.e. Snow) To The People
Posted via http://dbforums.com|||do a simple .BAT file to stop SQL service before backup runs and another
.BAT file after backup done to start SQL service. You can place the path to
run these files into Backup Exec job. I never use MSDE so I ain't sure but
for SQL you can similar to this:
BEFORE.BAT
net stop mssqlserver
AFTER.BAT
net start mssqlserver
Are you trying to backup the .MDF and LDF files? I prefer using native SQL
backup tools to backup databases.
hth,
"JakobDi" <Jakob_di@.hotmail.com> wrote in message
news:3381077.1063810544@.dbforums.com...
> I've installed MSDE SP3, and I'm looking for a script that runs once
> before back-up to shut down the server, and once after backing-up, to
> restart the server. This is supposed to go automatically. I'm running
> Veritas Back_up Exec 9.0 (Without SQL extension... ).
>
> Does anyone have an easy script for to run on my Win2k Server?
>
> --
> Jakob /n Powder (i.e. Snow) To The People
>
> Posted via http://dbforums.com|||Thanks All;
net stop mssql$test2 & net start msssql$test2 performed as expected,
(and the solution was rather simple; didn't think it would be
this easy...)
:-)
Originally posted by Flicker
> do a simple .BAT file to stop SQL service before backup runs
> and another
> .BAT file after backup done to start SQL service. You can place
> the path to
> run these files into Backup Exec job. I never use MSDE so I ain't
> sure but
> for SQL you can similar to this:
>
> BEFORE.BAT
> net stop mssqlserver
>
> AFTER.BAT
> net start mssqlserver
>
>
> Are you trying to backup the .MDF and LDF files? I prefer using
> native SQL
> backup tools to backup databases.
>
> hth,
>
>
>
>
> "JakobDi" <Jakob_di@.hotmail.com> wrote in message
> news:3381077.1063810544@.dbforums.com"]news:3381077.1063810544@.d-
> bforums.com[/url]...
> > I've installed MSDE SP3, and I'm looking for a script that runs
> once
> > before back-up to shut down the server, and once after backing-
> up, to
> > restart the server. This is supposed to go automatically. I'm
> running
> > Veritas Back_up Exec 9.0 (Without SQL extension... ).
> > Does anyone have an easy script for to run on my Win2k
> Server?
> > --
> > Jakob /n Powder (i.e. Snow) To The People
> Posted via
http://dbforums.com/http://dbforums.com
Jakob /n Powder (i.e. Snow) To The People
Posted via http://dbforums.com

Sunday, March 11, 2012

AWE? / Windows 2003 R2 x64 / SQL Server 2000 x86 / 8GB RAM

We had to install SQL 2000 on a 64-bit Intel x64 server. We quickly
learned that SQL 2000 x64 can only be installed on 64-bit Intel
Itanium (IA64) servers, so were forced to install the 32bit x86
version.
When running a 64-bit version of Windows 2003 with 8gb of RAM, we no
longer need to set the /3GB and /PAE switches because all of the
memory is addressable on the 64-bit platform.
Now that we are running 32-bit SQL Server 2000 Enterprise x86 on 64bit
Windows 2003 R2 Enterprise x64, do we need to enable AWE in SQL Server
like we had to on 32-bit Windows?
Here's how we did it on 32bit SQL:
http://www.sql-server-performance.com/awe_memory.asp
It appears that AWE is only required/supported on 32-bit OS:
http://www.microsoft.com/sql/editions/64bit/sql64bitadvantages.mspx
AWE is a set of memory management extensions to the Microsoft Win32?
API that allows applications to address memory beyond the 4GB
limitation. Using AWE, applications can acquire physical memory as
nonpaged memory, and then dynamically map views of the nonpaged memory
to the 32-bit address space.
32 it SQL Server is 32 bit. In order of a 32 bit app to see more than 2 or 3 GB memory, it need to
use the AWE extensions. So, yes, you need to sp_configure your 32 bit SQL Server to use AWE.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<mikemiller.innova@.gmail.com> wrote in message
news:1176395603.695552.226090@.b75g2000hsg.googlegr oups.com...
We had to install SQL 2000 on a 64-bit Intel x64 server. We quickly
learned that SQL 2000 x64 can only be installed on 64-bit Intel
Itanium (IA64) servers, so were forced to install the 32bit x86
version.
When running a 64-bit version of Windows 2003 with 8gb of RAM, we no
longer need to set the /3GB and /PAE switches because all of the
memory is addressable on the 64-bit platform.
Now that we are running 32-bit SQL Server 2000 Enterprise x86 on 64bit
Windows 2003 R2 Enterprise x64, do we need to enable AWE in SQL Server
like we had to on 32-bit Windows?
Here's how we did it on 32bit SQL:
http://www.sql-server-performance.com/awe_memory.asp
It appears that AWE is only required/supported on 32-bit OS:
http://www.microsoft.com/sql/editions/64bit/sql64bitadvantages.mspx
AWE is a set of memory management extensions to the Microsoft Win32?
API that allows applications to address memory beyond the 4GB
limitation. Using AWE, applications can acquire physical memory as
nonpaged memory, and then dynamically map views of the nonpaged memory
to the 32-bit address space.

AWE? / Windows 2003 R2 x64 / SQL Server 2000 x86 / 8GB RAM

We had to install SQL 2000 on a 64-bit Intel x64 server. We quickly learned that SQL 2000 x64 can only be installed on 64-bit Intel Itanium (IA64) servers, so were forced to install the 32bit x86 version.
When running a 64-bit version of Windows 2003 with 8gb of RAM, we no longer need to set the /3GB and /PAE switches because all of the memory is addressable on the 64-bit platform.
Now that we are running 32-bit SQL Server 2000 Enterprise x86 on 64bit Windows 2003 R2 Enterprise x64, do we need to enable AWE in SQL Server like we had to on 32-bit Windows?
Here's how we did it on 32bit SQL:
http://www.sql-server-performance.com/awe_memory.asp
It appears that AWE is only required/supported on 32-bit OS:
http://www.microsoft.com/sql/editio...advantages.mspx AWE is a set of memory management extensions to the Microsoft Win32 API that allows applications to address memory beyond the 4GB limitation. Using AWE, applications can acquire physical memory as nonpaged memory, and then dynamically map views of the nonpaged memory to the 32-bit address space.32 it SQL Server is 32 bit. In order of a 32 bit app to see more than 2 or 3
GB memory, it need to
use the AWE extensions. So, yes, you need to sp_configure your 32 bit SQL Se
rver to use AWE.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<mikemiller.innova@.gmail.com> wrote in message
news:1176395603.695552.226090@.b75g2000hsg.googlegroups.com...
We had to install SQL 2000 on a 64-bit Intel x64 server. We quickly
learned that SQL 2000 x64 can only be installed on 64-bit Intel
Itanium (IA64) servers, so were forced to install the 32bit x86
version.
When running a 64-bit version of Windows 2003 with 8gb of RAM, we no
longer need to set the /3GB and /PAE switches because all of the
memory is addressable on the 64-bit platform.
Now that we are running 32-bit SQL Server 2000 Enterprise x86 on 64bit
Windows 2003 R2 Enterprise x64, do we need to enable AWE in SQL Server
like we had to on 32-bit Windows?
Here's how we did it on 32bit SQL:
http://www.sql-server-performance.com/awe_memory.asp
It appears that AWE is only required/supported on 32-bit OS:
http://www.microsoft.com/sql/editio...advantages.mspx
AWE is a set of memory management extensions to the Microsoft Win32?
API that allows applications to address memory beyond the 4GB
limitation. Using AWE, applications can acquire physical memory as
nonpaged memory, and then dynamically map views of the nonpaged memory
to the 32-bit address space.

AWE, 3GB and SQL Boost

Please help. Just installed the SQL 2005 enterprise on 2003 standard server with /3GB switch.
Now, in SQL there is an AWE option. Do I need to check that off and where do I set the memory manualy and not dinamicly?
Also, do I boost SQL priority in processors?
Can you please help and give some other tunning pointers? I set couple of boxes with 2000 SQL and always used 3GB switch but forgot the priority on processors and other fine tunning steps. Thanks in advance.George,
How much memory do you have on the server? How much do you want to give to
SQL?
Chris
"George" <George@.discussions.microsoft.com> wrote in message
news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> Please help. Just installed the SQL 2005 enterprise on 2003 standard
> server
> with /3GB switch.
> Now, in SQL there is an AWE option. Do I need to check that off and where
> do
> I set the memory manualy and not dinamicly?
> Also, do I boost SQL priority in processors?
> Can you please help and give some other tunning pointers? I set couple of
> boxes with 2000 SQL and always used 3GB switch but forgot the priority on
> processors and other fine tunning steps. Thanks in advance.
>|||4GB on the server and 3GB to SQL
"Chris Wood" wrote:
> George,
> How much memory do you have on the server? How much do you want to give to
> SQL?
> Chris
> "George" <George@.discussions.microsoft.com> wrote in message
> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
> > server
> > with /3GB switch.
> > Now, in SQL there is an AWE option. Do I need to check that off and where
> > do
> > I set the memory manualy and not dinamicly?
> > Also, do I boost SQL priority in processors?
> > Can you please help and give some other tunning pointers? I set couple of
> > boxes with 2000 SQL and always used 3GB switch but forgot the priority on
> > processors and other fine tunning steps. Thanks in advance.
> >
>
>|||George,
On server 2003 the switches should be set by the O/S. You will need to
configure AWE using sp_configure and then set max and min memory. I would
try with 2.5Gb first before you see if you can move up to 3Gb.
Chris
"George" <George@.discussions.microsoft.com> wrote in message
news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
> 4GB on the server and 3GB to SQL
> "Chris Wood" wrote:
>> George,
>> How much memory do you have on the server? How much do you want to give
>> to
>> SQL?
>> Chris
>> "George" <George@.discussions.microsoft.com> wrote in message
>> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
>> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
>> > server
>> > with /3GB switch.
>> > Now, in SQL there is an AWE option. Do I need to check that off and
>> > where
>> > do
>> > I set the memory manualy and not dinamicly?
>> > Also, do I boost SQL priority in processors?
>> > Can you please help and give some other tunning pointers? I set couple
>> > of
>> > boxes with 2000 SQL and always used 3GB switch but forgot the priority
>> > on
>> > processors and other fine tunning steps. Thanks in advance.
>> >
>>|||Ok. So
1. Set the 3GB switch in Boot.ini (did this before SQL installation)
2. Run the sp_configure and set it to 2.5
Please confirm. Also, is that check for AWE in GUI same as the sp command
via QA?
"Chris Wood" wrote:
> George,
> On server 2003 the switches should be set by the O/S. You will need to
> configure AWE using sp_configure and then set max and min memory. I would
> try with 2.5Gb first before you see if you can move up to 3Gb.
> Chris
> "George" <George@.discussions.microsoft.com> wrote in message
> news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
> > 4GB on the server and 3GB to SQL
> >
> > "Chris Wood" wrote:
> >
> >> George,
> >>
> >> How much memory do you have on the server? How much do you want to give
> >> to
> >> SQL?
> >>
> >> Chris
> >>
> >> "George" <George@.discussions.microsoft.com> wrote in message
> >> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> >> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
> >> > server
> >> > with /3GB switch.
> >> > Now, in SQL there is an AWE option. Do I need to check that off and
> >> > where
> >> > do
> >> > I set the memory manualy and not dinamicly?
> >> > Also, do I boost SQL priority in processors?
> >> > Can you please help and give some other tunning pointers? I set couple
> >> > of
> >> > boxes with 2000 SQL and always used 3GB switch but forgot the priority
> >> > on
> >> > processors and other fine tunning steps. Thanks in advance.
> >> >
> >>
> >>
> >>
>
>|||Yes, checking and applying the 'Use AWE to allocate memory' checkbox is the
same as executing the following T-SQL code:
EXEC sys.sp_configure N'awe enabled', N'1'
RECONFIGURE WITH OVERRIDE
BTW, you almost never should boost the SQL process priority. In fact, Books
Online comes with the following warning:
"Raising the priority too high may drain resources from essential operating
system and network functions, resulting in problems shutting down SQL Server
or using other operating system tasks on the server."
Linchi
"George" wrote:
> Ok. So
> 1. Set the 3GB switch in Boot.ini (did this before SQL installation)
> 2. Run the sp_configure and set it to 2.5
> Please confirm. Also, is that check for AWE in GUI same as the sp command
> via QA?
> "Chris Wood" wrote:
> > George,
> >
> > On server 2003 the switches should be set by the O/S. You will need to
> > configure AWE using sp_configure and then set max and min memory. I would
> > try with 2.5Gb first before you see if you can move up to 3Gb.
> >
> > Chris
> >
> > "George" <George@.discussions.microsoft.com> wrote in message
> > news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
> > > 4GB on the server and 3GB to SQL
> > >
> > > "Chris Wood" wrote:
> > >
> > >> George,
> > >>
> > >> How much memory do you have on the server? How much do you want to give
> > >> to
> > >> SQL?
> > >>
> > >> Chris
> > >>
> > >> "George" <George@.discussions.microsoft.com> wrote in message
> > >> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> > >> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
> > >> > server
> > >> > with /3GB switch.
> > >> > Now, in SQL there is an AWE option. Do I need to check that off and
> > >> > where
> > >> > do
> > >> > I set the memory manualy and not dinamicly?
> > >> > Also, do I boost SQL priority in processors?
> > >> > Can you please help and give some other tunning pointers? I set couple
> > >> > of
> > >> > boxes with 2000 SQL and always used 3GB switch but forgot the priority
> > >> > on
> > >> > processors and other fine tunning steps. Thanks in advance.
> > >> >
> > >>
> > >>
> > >>
> >
> >
> >|||Thank you. I checked my prvious installations and you are right. I don't have
it on.
Now, as far as 3GB goes, do I keep it in the boot.ini and do I need some
other switch in addition?
If I put same valuses in both min and max memory, would that mean it is now
FIXED MEMORY SIZE assigned vs dynamically when there is a range?
SQL 2000 had a slider and a check box to choose from fixed and dynamyc (I am
sure you know of that just making a point)
"Linchi Shea" wrote:
> Yes, checking and applying the 'Use AWE to allocate memory' checkbox is the
> same as executing the following T-SQL code:
> EXEC sys.sp_configure N'awe enabled', N'1'
> RECONFIGURE WITH OVERRIDE
> BTW, you almost never should boost the SQL process priority. In fact, Books
> Online comes with the following warning:
> "Raising the priority too high may drain resources from essential operating
> system and network functions, resulting in problems shutting down SQL Server
> or using other operating system tasks on the server."
> Linchi
> "George" wrote:
> > Ok. So
> > 1. Set the 3GB switch in Boot.ini (did this before SQL installation)
> > 2. Run the sp_configure and set it to 2.5
> >
> > Please confirm. Also, is that check for AWE in GUI same as the sp command
> > via QA?
> >
> > "Chris Wood" wrote:
> >
> > > George,
> > >
> > > On server 2003 the switches should be set by the O/S. You will need to
> > > configure AWE using sp_configure and then set max and min memory. I would
> > > try with 2.5Gb first before you see if you can move up to 3Gb.
> > >
> > > Chris
> > >
> > > "George" <George@.discussions.microsoft.com> wrote in message
> > > news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
> > > > 4GB on the server and 3GB to SQL
> > > >
> > > > "Chris Wood" wrote:
> > > >
> > > >> George,
> > > >>
> > > >> How much memory do you have on the server? How much do you want to give
> > > >> to
> > > >> SQL?
> > > >>
> > > >> Chris
> > > >>
> > > >> "George" <George@.discussions.microsoft.com> wrote in message
> > > >> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> > > >> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
> > > >> > server
> > > >> > with /3GB switch.
> > > >> > Now, in SQL there is an AWE option. Do I need to check that off and
> > > >> > where
> > > >> > do
> > > >> > I set the memory manualy and not dinamicly?
> > > >> > Also, do I boost SQL priority in processors?
> > > >> > Can you please help and give some other tunning pointers? I set couple
> > > >> > of
> > > >> > boxes with 2000 SQL and always used 3GB switch but forgot the priority
> > > >> > on
> > > >> > processors and other fine tunning steps. Thanks in advance.
> > > >> >
> > > >>
> > > >>
> > > >>
> > >
> > >
> > >|||Can anyone please confirm I should keep the 3GB in boot.ini and enable AWE in
SQL?
"Linchi Shea" wrote:
> Yes, checking and applying the 'Use AWE to allocate memory' checkbox is the
> same as executing the following T-SQL code:
> EXEC sys.sp_configure N'awe enabled', N'1'
> RECONFIGURE WITH OVERRIDE
> BTW, you almost never should boost the SQL process priority. In fact, Books
> Online comes with the following warning:
> "Raising the priority too high may drain resources from essential operating
> system and network functions, resulting in problems shutting down SQL Server
> or using other operating system tasks on the server."
> Linchi
> "George" wrote:
> > Ok. So
> > 1. Set the 3GB switch in Boot.ini (did this before SQL installation)
> > 2. Run the sp_configure and set it to 2.5
> >
> > Please confirm. Also, is that check for AWE in GUI same as the sp command
> > via QA?
> >
> > "Chris Wood" wrote:
> >
> > > George,
> > >
> > > On server 2003 the switches should be set by the O/S. You will need to
> > > configure AWE using sp_configure and then set max and min memory. I would
> > > try with 2.5Gb first before you see if you can move up to 3Gb.
> > >
> > > Chris
> > >
> > > "George" <George@.discussions.microsoft.com> wrote in message
> > > news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
> > > > 4GB on the server and 3GB to SQL
> > > >
> > > > "Chris Wood" wrote:
> > > >
> > > >> George,
> > > >>
> > > >> How much memory do you have on the server? How much do you want to give
> > > >> to
> > > >> SQL?
> > > >>
> > > >> Chris
> > > >>
> > > >> "George" <George@.discussions.microsoft.com> wrote in message
> > > >> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> > > >> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
> > > >> > server
> > > >> > with /3GB switch.
> > > >> > Now, in SQL there is an AWE option. Do I need to check that off and
> > > >> > where
> > > >> > do
> > > >> > I set the memory manualy and not dinamicly?
> > > >> > Also, do I boost SQL priority in processors?
> > > >> > Can you please help and give some other tunning pointers? I set couple
> > > >> > of
> > > >> > boxes with 2000 SQL and always used 3GB switch but forgot the priority
> > > >> > on
> > > >> > processors and other fine tunning steps. Thanks in advance.
> > > >> >
> > > >>
> > > >>
> > > >>
> > >
> > >
> > >|||Chris, thanks. I can not go higher than 2.1 GB. Please help.
"Chris Wood" wrote:
> George,
> On server 2003 the switches should be set by the O/S. You will need to
> configure AWE using sp_configure and then set max and min memory. I would
> try with 2.5Gb first before you see if you can move up to 3Gb.
> Chris
> "George" <George@.discussions.microsoft.com> wrote in message
> news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
> > 4GB on the server and 3GB to SQL
> >
> > "Chris Wood" wrote:
> >
> >> George,
> >>
> >> How much memory do you have on the server? How much do you want to give
> >> to
> >> SQL?
> >>
> >> Chris
> >>
> >> "George" <George@.discussions.microsoft.com> wrote in message
> >> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> >> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
> >> > server
> >> > with /3GB switch.
> >> > Now, in SQL there is an AWE option. Do I need to check that off and
> >> > where
> >> > do
> >> > I set the memory manualy and not dinamicly?
> >> > Also, do I boost SQL priority in processors?
> >> > Can you please help and give some other tunning pointers? I set couple
> >> > of
> >> > boxes with 2000 SQL and always used 3GB switch but forgot the priority
> >> > on
> >> > processors and other fine tunning steps. Thanks in advance.
> >> >
> >>
> >>
> >>
>
>|||George,
Have you seen this:- http://support.microsoft.com/kb/283037/en-us
Chris
"George" <George@.discussions.microsoft.com> wrote in message
news:F90DAA9C-1226-4E6F-9445-D4C3696A4556@.microsoft.com...
> Chris, thanks. I can not go higher than 2.1 GB. Please help.
> "Chris Wood" wrote:
>> George,
>> On server 2003 the switches should be set by the O/S. You will need to
>> configure AWE using sp_configure and then set max and min memory. I would
>> try with 2.5Gb first before you see if you can move up to 3Gb.
>> Chris
>> "George" <George@.discussions.microsoft.com> wrote in message
>> news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
>> > 4GB on the server and 3GB to SQL
>> >
>> > "Chris Wood" wrote:
>> >
>> >> George,
>> >>
>> >> How much memory do you have on the server? How much do you want to
>> >> give
>> >> to
>> >> SQL?
>> >>
>> >> Chris
>> >>
>> >> "George" <George@.discussions.microsoft.com> wrote in message
>> >> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
>> >> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
>> >> > server
>> >> > with /3GB switch.
>> >> > Now, in SQL there is an AWE option. Do I need to check that off and
>> >> > where
>> >> > do
>> >> > I set the memory manualy and not dinamicly?
>> >> > Also, do I boost SQL priority in processors?
>> >> > Can you please help and give some other tunning pointers? I set
>> >> > couple
>> >> > of
>> >> > boxes with 2000 SQL and always used 3GB switch but forgot the
>> >> > priority
>> >> > on
>> >> > processors and other fine tunning steps. Thanks in advance.
>> >> >
>> >>
>> >>
>> >>
>>|||Yes. To be honest, it is vague as some other Microsoft documents. Not sure
how to interpret the doc 100%.
So far, I understand that as long as I have no more than 4GB, I can dedicate
3 GB to SQL and 1GB to Windows and other apps by using only /3GB switch in
Boot.ini. My understanding was not to use PAE or AWE.
"Chris Wood" wrote:
> George,
> Have you seen this:- http://support.microsoft.com/kb/283037/en-us
> Chris
> "George" <George@.discussions.microsoft.com> wrote in message
> news:F90DAA9C-1226-4E6F-9445-D4C3696A4556@.microsoft.com...
> > Chris, thanks. I can not go higher than 2.1 GB. Please help.
> >
> > "Chris Wood" wrote:
> >
> >> George,
> >>
> >> On server 2003 the switches should be set by the O/S. You will need to
> >> configure AWE using sp_configure and then set max and min memory. I would
> >> try with 2.5Gb first before you see if you can move up to 3Gb.
> >>
> >> Chris
> >>
> >> "George" <George@.discussions.microsoft.com> wrote in message
> >> news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
> >> > 4GB on the server and 3GB to SQL
> >> >
> >> > "Chris Wood" wrote:
> >> >
> >> >> George,
> >> >>
> >> >> How much memory do you have on the server? How much do you want to
> >> >> give
> >> >> to
> >> >> SQL?
> >> >>
> >> >> Chris
> >> >>
> >> >> "George" <George@.discussions.microsoft.com> wrote in message
> >> >> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> >> >> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
> >> >> > server
> >> >> > with /3GB switch.
> >> >> > Now, in SQL there is an AWE option. Do I need to check that off and
> >> >> > where
> >> >> > do
> >> >> > I set the memory manualy and not dinamicly?
> >> >> > Also, do I boost SQL priority in processors?
> >> >> > Can you please help and give some other tunning pointers? I set
> >> >> > couple
> >> >> > of
> >> >> > boxes with 2000 SQL and always used 3GB switch but forgot the
> >> >> > priority
> >> >> > on
> >> >> > processors and other fine tunning steps. Thanks in advance.
> >> >> >
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||George,
You are indicating that 2 Gig is the ceiling on your machine. This will
always be the case if you have the Standard Edition as opposed to the
Enterprise Edition of SQL Server 2000. You didn't indicate you were running
2005 which does not have this limitation.
I made this mistake myself, adding 6 GIG to a Windows 2000 Advanced Server.
We still run at 2 GIG with the Standard Edition. We are using the boot.ini
switch to enable Windows 2000 Advanced to access above the 4 Gig mark which
is the limit on Windows 2000 without the switch. 2003 server has similar
requirements, but I think it starts at 16 gig so there should not be a
problem on the boot.ini for a 4 GIG machine. It is only the fact that you
may be using the Standard Edition.
--
Regards,
Jamie
"George" wrote:
> Chris, thanks. I can not go higher than 2.1 GB. Please help.
> "Chris Wood" wrote:
> > George,
> >
> > On server 2003 the switches should be set by the O/S. You will need to
> > configure AWE using sp_configure and then set max and min memory. I would
> > try with 2.5Gb first before you see if you can move up to 3Gb.
> >
> > Chris
> >
> > "George" <George@.discussions.microsoft.com> wrote in message
> > news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
> > > 4GB on the server and 3GB to SQL
> > >
> > > "Chris Wood" wrote:
> > >
> > >> George,
> > >>
> > >> How much memory do you have on the server? How much do you want to give
> > >> to
> > >> SQL?
> > >>
> > >> Chris
> > >>
> > >> "George" <George@.discussions.microsoft.com> wrote in message
> > >> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> > >> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
> > >> > server
> > >> > with /3GB switch.
> > >> > Now, in SQL there is an AWE option. Do I need to check that off and
> > >> > where
> > >> > do
> > >> > I set the memory manualy and not dinamicly?
> > >> > Also, do I boost SQL priority in processors?
> > >> > Can you please help and give some other tunning pointers? I set couple
> > >> > of
> > >> > boxes with 2000 SQL and always used 3GB switch but forgot the priority
> > >> > on
> > >> > processors and other fine tunning steps. Thanks in advance.
> > >> >
> > >>
> > >>
> > >>
> >
> >
> >|||/3GB is a boot.ini setting. Not need to configure anything inside SQL Server
for this.
Linchi
"George" wrote:
> Thank you. I checked my prvious installations and you are right. I don't have
> it on.
> Now, as far as 3GB goes, do I keep it in the boot.ini and do I need some
> other switch in addition?
> If I put same valuses in both min and max memory, would that mean it is now
> FIXED MEMORY SIZE assigned vs dynamically when there is a range?
> SQL 2000 had a slider and a check box to choose from fixed and dynamyc (I am
> sure you know of that just making a point)
> "Linchi Shea" wrote:
> > Yes, checking and applying the 'Use AWE to allocate memory' checkbox is the
> > same as executing the following T-SQL code:
> >
> > EXEC sys.sp_configure N'awe enabled', N'1'
> > RECONFIGURE WITH OVERRIDE
> >
> > BTW, you almost never should boost the SQL process priority. In fact, Books
> > Online comes with the following warning:
> >
> > "Raising the priority too high may drain resources from essential operating
> > system and network functions, resulting in problems shutting down SQL Server
> > or using other operating system tasks on the server."
> >
> > Linchi
> >
> > "George" wrote:
> >
> > > Ok. So
> > > 1. Set the 3GB switch in Boot.ini (did this before SQL installation)
> > > 2. Run the sp_configure and set it to 2.5
> > >
> > > Please confirm. Also, is that check for AWE in GUI same as the sp command
> > > via QA?
> > >
> > > "Chris Wood" wrote:
> > >
> > > > George,
> > > >
> > > > On server 2003 the switches should be set by the O/S. You will need to
> > > > configure AWE using sp_configure and then set max and min memory. I would
> > > > try with 2.5Gb first before you see if you can move up to 3Gb.
> > > >
> > > > Chris
> > > >
> > > > "George" <George@.discussions.microsoft.com> wrote in message
> > > > news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
> > > > > 4GB on the server and 3GB to SQL
> > > > >
> > > > > "Chris Wood" wrote:
> > > > >
> > > > >> George,
> > > > >>
> > > > >> How much memory do you have on the server? How much do you want to give
> > > > >> to
> > > > >> SQL?
> > > > >>
> > > > >> Chris
> > > > >>
> > > > >> "George" <George@.discussions.microsoft.com> wrote in message
> > > > >> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> > > > >> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
> > > > >> > server
> > > > >> > with /3GB switch.
> > > > >> > Now, in SQL there is an AWE option. Do I need to check that off and
> > > > >> > where
> > > > >> > do
> > > > >> > I set the memory manualy and not dinamicly?
> > > > >> > Also, do I boost SQL priority in processors?
> > > > >> > Can you please help and give some other tunning pointers? I set couple
> > > > >> > of
> > > > >> > boxes with 2000 SQL and always used 3GB switch but forgot the priority
> > > > >> > on
> > > > >> > processors and other fine tunning steps. Thanks in advance.
> > > > >> >
> > > > >>
> > > > >>
> > > > >>
> > > >
> > > >
> > > >|||I have some empirical data on how much buffer pool mmeory a SQL instance
could consume with various settings of 3GB and AWE
http://sqlblog.com/blogs/linchi_shea/archive/2007/01/11/awe-and-3gb-an-empirical-picture.aspx
Linchi
"George" wrote:
> Yes. To be honest, it is vague as some other Microsoft documents. Not sure
> how to interpret the doc 100%.
> So far, I understand that as long as I have no more than 4GB, I can dedicate
> 3 GB to SQL and 1GB to Windows and other apps by using only /3GB switch in
> Boot.ini. My understanding was not to use PAE or AWE.
> "Chris Wood" wrote:
> > George,
> >
> > Have you seen this:- http://support.microsoft.com/kb/283037/en-us
> >
> > Chris
> >
> > "George" <George@.discussions.microsoft.com> wrote in message
> > news:F90DAA9C-1226-4E6F-9445-D4C3696A4556@.microsoft.com...
> > > Chris, thanks. I can not go higher than 2.1 GB. Please help.
> > >
> > > "Chris Wood" wrote:
> > >
> > >> George,
> > >>
> > >> On server 2003 the switches should be set by the O/S. You will need to
> > >> configure AWE using sp_configure and then set max and min memory. I would
> > >> try with 2.5Gb first before you see if you can move up to 3Gb.
> > >>
> > >> Chris
> > >>
> > >> "George" <George@.discussions.microsoft.com> wrote in message
> > >> news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
> > >> > 4GB on the server and 3GB to SQL
> > >> >
> > >> > "Chris Wood" wrote:
> > >> >
> > >> >> George,
> > >> >>
> > >> >> How much memory do you have on the server? How much do you want to
> > >> >> give
> > >> >> to
> > >> >> SQL?
> > >> >>
> > >> >> Chris
> > >> >>
> > >> >> "George" <George@.discussions.microsoft.com> wrote in message
> > >> >> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> > >> >> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
> > >> >> > server
> > >> >> > with /3GB switch.
> > >> >> > Now, in SQL there is an AWE option. Do I need to check that off and
> > >> >> > where
> > >> >> > do
> > >> >> > I set the memory manualy and not dinamicly?
> > >> >> > Also, do I boost SQL priority in processors?
> > >> >> > Can you please help and give some other tunning pointers? I set
> > >> >> > couple
> > >> >> > of
> > >> >> > boxes with 2000 SQL and always used 3GB switch but forgot the
> > >> >> > priority
> > >> >> > on
> > >> >> > processors and other fine tunning steps. Thanks in advance.
> > >> >> >
> > >> >>
> > >> >>
> > >> >>
> > >>
> > >>
> > >>
> >
> >
> >

AWE, 3GB and SQL Boost

Thursday, March 8, 2012

AWE question (Geoff N. Hiten)

Hello
We have windows 2003 server (8GB) with SQL Server 2004(sp4) +one small
application installed on it.
We also have \3gb parameter in the boot.ini
It is a cluster Active/Passive
What would you recommenf to insttall a hotfix to Passive first and then
Active or it does not matter?
Is it any problems installing a hotfix? What is about lock pages in memory?
And running AWE enabling on Passive first also?
Geoff , how much memory to give to SQL SERVER if small application is using
about 50MB AND SQL SERVER 2.7gb?
Thanks
Alex,
There is no SQL 2004. I am guessing since you mention SP4, that is SQL
2000, since SQL 2005 is only at SP2 for now.
Hotfixes install to all nodes on a cluster for a particular instance. You
need to start the install from the node that is currently hosting the
instance. You must grant lock pages in memory to the SQL service account in
order to get AWE to work. AWE is a setting for the SQL instance, so it will
take effect whichever node hosts that instance.
For an 8GB system, I would start by setting SQL at 6GB and see how free
memory looks. You may be able to inch it up a bit, but it is better to
leave a little extra free memory than to run out. The only down side is
with SQL 2000 you have to stop and restart the service to enact an AWE
memory change.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Alex" <test@.hotmail.com> wrote in message
news:ehk91SwkHHA.4248@.TK2MSFTNGP06.phx.gbl...
> Hello
> We have windows 2003 server (8GB) with SQL Server 2004(sp4) +one small
> application installed on it.
> We also have \3gb parameter in the boot.ini
>
> It is a cluster Active/Passive
> What would you recommenf to insttall a hotfix to Passive first and then
> Active or it does not matter?
> Is it any problems installing a hotfix? What is about lock pages in
> memory?
> And running AWE enabling on Passive first also?
>
> Geoff , how much memory to give to SQL SERVER if small application is
> using about 50MB AND SQL SERVER 2.7gb?
> Thanks
>
>
|||Thank you Geoff N. Hiten
Yes , we are using SQL Server 2000(SP4).
Please take alook at the follwing list and tell me whether it looks good to
you.
a) SQL node1 --(Active) has 8GB
b) SQL node1 --(Passive) has 8GB
1) Install hotfix from(http://support.microsoft.com/kb/899761) on SQL1 node
(Active)
2) Install hotfix from(http://support.microsoft.com/kb/899761) on SQL2 node
(Passive)
3) Grant 'lock pages in memory' on on SQL1 node (Active)
4) Grant 'lock pages in memory' on on SQL1 node (Passive)
5) Enabling AWE on SQL1 node (Active)--set to 6GB
6) Enabling AWE on SQL1 node (Passive)--set to 6GB
Thanks you again
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OZ4pcewkHHA.4904@.TK2MSFTNGP05.phx.gbl...
> Alex,
> There is no SQL 2004. I am guessing since you mention SP4, that is SQL
> 2000, since SQL 2005 is only at SP2 for now.
> Hotfixes install to all nodes on a cluster for a particular instance. You
> need to start the install from the node that is currently hosting the
> instance. You must grant lock pages in memory to the SQL service account
> in order to get AWE to work. AWE is a setting for the SQL instance, so it
> will take effect whichever node hosts that instance.
> For an 8GB system, I would start by setting SQL at 6GB and see how free
> memory looks. You may be able to inch it up a bit, but it is better to
> leave a little extra free memory than to run out. The only down side is
> with SQL 2000 you have to stop and restart the service to enact an AWE
> memory change.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Alex" <test@.hotmail.com> wrote in message
> news:ehk91SwkHHA.4248@.TK2MSFTNGP06.phx.gbl...
>

AWE question (Geoff N. Hiten)

Hello
We have windows 2003 server (8GB) with SQL Server 2004(sp4) +one small
application installed on it.
We also have \3gb parameter in the boot.ini
It is a cluster Active/Passive
What would you recommenf to insttall a hotfix to Passive first and then
Active or it does not matter?
Is it any problems installing a hotfix? What is about lock pages in memory?
And running AWE enabling on Passive first also?
Geoff , how much memory to give to SQL SERVER if small application is using
about 50MB AND SQL SERVER 2.7gb?
ThanksAlex,
There is no SQL 2004. I am guessing since you mention SP4, that is SQL
2000, since SQL 2005 is only at SP2 for now.
Hotfixes install to all nodes on a cluster for a particular instance. You
need to start the install from the node that is currently hosting the
instance. You must grant lock pages in memory to the SQL service account in
order to get AWE to work. AWE is a setting for the SQL instance, so it will
take effect whichever node hosts that instance.
For an 8GB system, I would start by setting SQL at 6GB and see how free
memory looks. You may be able to inch it up a bit, but it is better to
leave a little extra free memory than to run out. The only down side is
with SQL 2000 you have to stop and restart the service to enact an AWE
memory change.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Alex" <test@.hotmail.com> wrote in message
news:ehk91SwkHHA.4248@.TK2MSFTNGP06.phx.gbl...
> Hello
> We have windows 2003 server (8GB) with SQL Server 2004(sp4) +one small
> application installed on it.
> We also have \3gb parameter in the boot.ini
>
> It is a cluster Active/Passive
> What would you recommenf to insttall a hotfix to Passive first and then
> Active or it does not matter?
> Is it any problems installing a hotfix? What is about lock pages in
> memory?
> And running AWE enabling on Passive first also?
>
> Geoff , how much memory to give to SQL SERVER if small application is
> using about 50MB AND SQL SERVER 2.7gb?
> Thanks
>
>|||Thank you Geoff N. Hiten
Yes , we are using SQL Server 2000(SP4).
Please take alook at the follwing list and tell me whether it looks good to
you.
a) SQL node1 --(Active) has 8GB
b) SQL node1 --(Passive) has 8GB
1) Install hotfix from(http://support.microsoft.com/kb/899761) on SQL1 node
(Active)
2) Install hotfix from(http://support.microsoft.com/kb/899761) on SQL2 node
(Passive)
3) Grant 'lock pages in memory' on on SQL1 node (Active)
4) Grant 'lock pages in memory' on on SQL1 node (Passive)
5) Enabling AWE on SQL1 node (Active)--set to 6GB
6) Enabling AWE on SQL1 node (Passive)--set to 6GB
Thanks you again
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OZ4pcewkHHA.4904@.TK2MSFTNGP05.phx.gbl...
> Alex,
> There is no SQL 2004. I am guessing since you mention SP4, that is SQL
> 2000, since SQL 2005 is only at SP2 for now.
> Hotfixes install to all nodes on a cluster for a particular instance. You
> need to start the install from the node that is currently hosting the
> instance. You must grant lock pages in memory to the SQL service account
> in order to get AWE to work. AWE is a setting for the SQL instance, so it
> will take effect whichever node hosts that instance.
> For an 8GB system, I would start by setting SQL at 6GB and see how free
> memory looks. You may be able to inch it up a bit, but it is better to
> leave a little extra free memory than to run out. The only down side is
> with SQL 2000 you have to stop and restart the service to enact an AWE
> memory change.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Alex" <test@.hotmail.com> wrote in message
> news:ehk91SwkHHA.4248@.TK2MSFTNGP06.phx.gbl...
>> Hello
>> We have windows 2003 server (8GB) with SQL Server 2004(sp4) +one small
>> application installed on it.
>> We also have \3gb parameter in the boot.ini
>>
>> It is a cluster Active/Passive
>> What would you recommenf to insttall a hotfix to Passive first and then
>> Active or it does not matter?
>> Is it any problems installing a hotfix? What is about lock pages in
>> memory?
>> And running AWE enabling on Passive first also?
>>
>> Geoff , how much memory to give to SQL SERVER if small application is
>> using about 50MB AND SQL SERVER 2.7gb?
>> Thanks
>>
>>
>

AWE question (Geoff N. Hiten)

Hello
We have windows 2003 server (8GB) with SQL Server 2004(sp4) +one small
application installed on it.
We also have \3gb parameter in the boot.ini
It is a cluster Active/Passive
What would you recommenf to insttall a hotfix to Passive first and then
Active or it does not matter?
Is it any problems installing a hotfix? What is about lock pages in memory?
And running AWE enabling on Passive first also?
Geoff , how much memory to give to SQL SERVER if small application is using
about 50MB AND SQL SERVER 2.7gb?
ThanksAlex,
There is no SQL 2004. I am guessing since you mention SP4, that is SQL
2000, since SQL 2005 is only at SP2 for now.
Hotfixes install to all nodes on a cluster for a particular instance. You
need to start the install from the node that is currently hosting the
instance. You must grant lock pages in memory to the SQL service account in
order to get AWE to work. AWE is a setting for the SQL instance, so it will
take effect whichever node hosts that instance.
For an 8GB system, I would start by setting SQL at 6GB and see how free
memory looks. You may be able to inch it up a bit, but it is better to
leave a little extra free memory than to run out. The only down side is
with SQL 2000 you have to stop and restart the service to enact an AWE
memory change.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Alex" <test@.hotmail.com> wrote in message
news:ehk91SwkHHA.4248@.TK2MSFTNGP06.phx.gbl...
> Hello
> We have windows 2003 server (8GB) with SQL Server 2004(sp4) +one small
> application installed on it.
> We also have \3gb parameter in the boot.ini
>
> It is a cluster Active/Passive
> What would you recommenf to insttall a hotfix to Passive first and then
> Active or it does not matter?
> Is it any problems installing a hotfix? What is about lock pages in
> memory?
> And running AWE enabling on Passive first also?
>
> Geoff , how much memory to give to SQL SERVER if small application is
> using about 50MB AND SQL SERVER 2.7gb?
> Thanks
>
>|||Thank you Geoff N. Hiten
Yes , we are using SQL Server 2000(SP4).
Please take alook at the follwing list and tell me whether it looks good to
you.
a) SQL node1 --(Active) has 8GB
b) SQL node1 --(Passive) has 8GB
1) Install hotfix from(http://support.microsoft.com/kb/899761) on SQL1 node
(Active)
2) Install hotfix from(http://support.microsoft.com/kb/899761) on SQL2 node
(Passive)
3) Grant 'lock pages in memory' on on SQL1 node (Active)
4) Grant 'lock pages in memory' on on SQL1 node (Passive)
5) Enabling AWE on SQL1 node (Active)--set to 6GB
6) Enabling AWE on SQL1 node (Passive)--set to 6GB
Thanks you again
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OZ4pcewkHHA.4904@.TK2MSFTNGP05.phx.gbl...
> Alex,
> There is no SQL 2004. I am guessing since you mention SP4, that is SQL
> 2000, since SQL 2005 is only at SP2 for now.
> Hotfixes install to all nodes on a cluster for a particular instance. You
> need to start the install from the node that is currently hosting the
> instance. You must grant lock pages in memory to the SQL service account
> in order to get AWE to work. AWE is a setting for the SQL instance, so it
> will take effect whichever node hosts that instance.
> For an 8GB system, I would start by setting SQL at 6GB and see how free
> memory looks. You may be able to inch it up a bit, but it is better to
> leave a little extra free memory than to run out. The only down side is
> with SQL 2000 you have to stop and restart the service to enact an AWE
> memory change.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Alex" <test@.hotmail.com> wrote in message
> news:ehk91SwkHHA.4248@.TK2MSFTNGP06.phx.gbl...
>

AWE Memory on SQL Server 2000(SP4)

Hello everybody
We have windows 2003 server (8GB) with SQL Server 2004(sp4) +one small
application installed on it.
We also have \3gb parameter in the boot.ini
SQL Server is using 2,7 GB.
Application is using three processes , that each one is about 50 MB .
I took a Page Life expectancy counter which was under 300 for about 10-15
minuets and after grown up till 320 ... and then droped again...and up
again..
Do you think I need to enable AWE? If you do , how much memory to give to
SQL Server?
I have heard that there is a problem with SP4 and AWE, am I right?
Thank you.Definitely enable AWE. Also make sure that /PAE is in the boot.ini file.
You will need to apply at least one hotfix after SP4 to get AWE to woork
correctly.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Alex" <test@.hotmail.com> wrote in message
news:uzB1UnkkHHA.1240@.TK2MSFTNGP04.phx.gbl...
> Hello everybody
> We have windows 2003 server (8GB) with SQL Server 2004(sp4) +one small
> application installed on it.
> We also have \3gb parameter in the boot.ini
> SQL Server is using 2,7 GB.
> Application is using three processes , that each one is about 50 MB .
> I took a Page Life expectancy counter which was under 300 for about 10-15
> minuets and after grown up till 320 ... and then droped again...and up
> again..
> Do you think I need to enable AWE? If you do , how much memory to give to
> SQL Server?
> I have heard that there is a problem with SP4 and AWE, am I right?
> Thank you.
>
>
>
>|||"Alex" <test@.hotmail.com> wrote in message
news:uzB1UnkkHHA.1240@.TK2MSFTNGP04.phx.gbl...
> Hello everybody
> We have windows 2003 server (8GB) with SQL Server 2004(sp4) +one small
> application installed on it.
> We also have \3gb parameter in the boot.ini
> SQL Server is using 2,7 GB.
> Application is using three processes , that each one is about 50 MB .
> I took a Page Life expectancy counter which was under 300 for about 10-15
> minuets and after grown up till 320 ... and then droped again...and up
> again..
> Do you think I need to enable AWE? If you do , how much memory to give to
> SQL Server?
> I have heard that there is a problem with SP4 and AWE, am I right?
> Thank you.
I believe you need Enterprise versions of SQL Server and your OS to use AWE.
If you have these I would add /PAE and /3GB to boot.ini, install the SP4
hotfix pertaining to AWE and then enable AWE in SQL Server limiting SQL
Server to 6GB
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
When you restart SQL Server you should see Address Windowing Extensions
Enabled in the log.
You can also use the SQL Performance counter-Total Server Memory to confirm
that SQL is using 6GB.
Read these:
http://support.microsoft.com/kb/274750
http://www.sql-server-performance.com/awe_memory.asp|||Hi,
What is the hotfix after SP4 installed ?
Do I need to apply the hotfix if I am running SP3a on SQL2000 ?
JT
"Terri" wrote:
> "Alex" <test@.hotmail.com> wrote in message
> news:uzB1UnkkHHA.1240@.TK2MSFTNGP04.phx.gbl...
> > Hello everybody
> > We have windows 2003 server (8GB) with SQL Server 2004(sp4) +one small
> > application installed on it.
> >
> > We also have \3gb parameter in the boot.ini
> >
> > SQL Server is using 2,7 GB.
> > Application is using three processes , that each one is about 50 MB .
> >
> > I took a Page Life expectancy counter which was under 300 for about 10-15
> > minuets and after grown up till 320 ... and then droped again...and up
> > again..
> >
> > Do you think I need to enable AWE? If you do , how much memory to give to
> > SQL Server?
> > I have heard that there is a problem with SP4 and AWE, am I right?
> >
> > Thank you.
> I believe you need Enterprise versions of SQL Server and your OS to use AWE.
> If you have these I would add /PAE and /3GB to boot.ini, install the SP4
> hotfix pertaining to AWE and then enable AWE in SQL Server limiting SQL
> Server to 6GB
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> sp_configure 'max server memory', 6144
> RECONFIGURE
> GO
>
> When you restart SQL Server you should see Address Windowing Extensions
> Enabled in the log.
>
> You can also use the SQL Performance counter-Total Server Memory to confirm
> that SQL is using 6GB.
>
> Read these:
> http://support.microsoft.com/kb/274750
> http://www.sql-server-performance.com/awe_memory.asp
>
>
>|||The hotfix (build 2040) fixes a bug introduced in SP4 related to AWE on
32-bit host computers. The hotfix is only necessary if you have installed
SP4 and yout host computer has more than 4GB of physicl memory.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Johnny" <Johnny@.discussions.microsoft.com> wrote in message
news:D1A4714E-D506-4D9F-912E-C44AB8595E92@.microsoft.com...
> Hi,
> What is the hotfix after SP4 installed ?
> Do I need to apply the hotfix if I am running SP3a on SQL2000 ?
> JT
> "Terri" wrote:
>> "Alex" <test@.hotmail.com> wrote in message
>> news:uzB1UnkkHHA.1240@.TK2MSFTNGP04.phx.gbl...
>> > Hello everybody
>> > We have windows 2003 server (8GB) with SQL Server 2004(sp4) +one small
>> > application installed on it.
>> >
>> > We also have \3gb parameter in the boot.ini
>> >
>> > SQL Server is using 2,7 GB.
>> > Application is using three processes , that each one is about 50 MB .
>> >
>> > I took a Page Life expectancy counter which was under 300 for about
>> > 10-15
>> > minuets and after grown up till 320 ... and then droped again...and
>> > up
>> > again..
>> >
>> > Do you think I need to enable AWE? If you do , how much memory to give
>> > to
>> > SQL Server?
>> > I have heard that there is a problem with SP4 and AWE, am I right?
>> >
>> > Thank you.
>> I believe you need Enterprise versions of SQL Server and your OS to use
>> AWE.
>> If you have these I would add /PAE and /3GB to boot.ini, install the SP4
>> hotfix pertaining to AWE and then enable AWE in SQL Server limiting SQL
>> Server to 6GB
>> sp_configure 'show advanced options', 1
>> RECONFIGURE
>> GO
>> sp_configure 'awe enabled', 1
>> RECONFIGURE
>> GO
>> sp_configure 'max server memory', 6144
>> RECONFIGURE
>> GO
>>
>> When you restart SQL Server you should see Address Windowing Extensions
>> Enabled in the log.
>>
>> You can also use the SQL Performance counter-Total Server Memory to
>> confirm
>> that SQL is using 6GB.
>>
>> Read these:
>> http://support.microsoft.com/kb/274750
>> http://www.sql-server-performance.com/awe_memory.asp
>>
>>

Monday, February 13, 2012

Avast Antivirus causing SQL Server 2005 not to start up

I have SQL Server 2005 and Visual Studio .NET 2005 installed on my
developer PC. I installed SQL Server 2005 SP2 last week and installed
Avast Antivirus this week. What I noticed was that after my reboot, I
could not get SQL Server to start. In the Surface Area Configuration,
I was getting error messages in regards to me not having permission to
start the service.
So I uninstalled Avast Antivirus (Home Edition btw), and rebooted.
Alas, SQL Server 2005 was starting up again!
I use AVG Antivirus (free of course), and was wondering if anybody
else out there has had similar problems? Is it just Avast?
Thanks.
"tofu.captain" <tofu.captain@.gmail.com> wrote in message
news:1176693441.180857.3870@.w1g2000hsg.googlegroup s.com...
>I have SQL Server 2005 and Visual Studio .NET 2005 installed on my
> developer PC. I installed SQL Server 2005 SP2 last week and installed
> Avast Antivirus this week. What I noticed was that after my reboot, I
> could not get SQL Server to start. In the Surface Area Configuration,
> I was getting error messages in regards to me not having permission to
> start the service.
> So I uninstalled Avast Antivirus (Home Edition btw), and rebooted.
> Alas, SQL Server 2005 was starting up again!
> I use AVG Antivirus (free of course), and was wondering if anybody
> else out there has had similar problems? Is it just Avast?
Generally suggest not running an AV on a SQL Server. At the very least
suggest telling it to not scan the databases.

> Thanks.
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
|||Hi
"tofu.captain" wrote:

> I have SQL Server 2005 and Visual Studio .NET 2005 installed on my
> developer PC. I installed SQL Server 2005 SP2 last week and installed
> Avast Antivirus this week. What I noticed was that after my reboot, I
> could not get SQL Server to start. In the Surface Area Configuration,
> I was getting error messages in regards to me not having permission to
> start the service.
> So I uninstalled Avast Antivirus (Home Edition btw), and rebooted.
> Alas, SQL Server 2005 was starting up again!
> I use AVG Antivirus (free of course), and was wondering if anybody
> else out there has had similar problems? Is it just Avast?
> Thanks.
>
As this is a developer PC you probably do want to install an antivirus
program, but as Greg says do not scan the database files as SQL Server will
require exclusive access to these files. I would expect user databases to be
marked as suspect if the scan was occurring during start up, but SQL Server
may still start therefore the error message seems slightly spurious. Have you
checked the SQL Server log and the event log for any additional information?
John

Avast Antivirus causing SQL Server 2005 not to start up

I have SQL Server 2005 and Visual Studio .NET 2005 installed on my
developer PC. I installed SQL Server 2005 SP2 last week and installed
Avast Antivirus this week. What I noticed was that after my reboot, I
could not get SQL Server to start. In the Surface Area Configuration,
I was getting error messages in regards to me not having permission to
start the service.
So I uninstalled Avast Antivirus (Home Edition btw), and rebooted.
Alas, SQL Server 2005 was starting up again!
I use AVG Antivirus (free of course), and was wondering if anybody
else out there has had similar problems? Is it just Avast?
Thanks."tofu.captain" <tofu.captain@.gmail.com> wrote in message
news:1176693441.180857.3870@.w1g2000hsg.googlegroups.com...
>I have SQL Server 2005 and Visual Studio .NET 2005 installed on my
> developer PC. I installed SQL Server 2005 SP2 last week and installed
> Avast Antivirus this week. What I noticed was that after my reboot, I
> could not get SQL Server to start. In the Surface Area Configuration,
> I was getting error messages in regards to me not having permission to
> start the service.
> So I uninstalled Avast Antivirus (Home Edition btw), and rebooted.
> Alas, SQL Server 2005 was starting up again!
> I use AVG Antivirus (free of course), and was wondering if anybody
> else out there has had similar problems? Is it just Avast?
Generally suggest not running an AV on a SQL Server. At the very least
suggest telling it to not scan the databases.

> Thanks.
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Hi
"tofu.captain" wrote:

> I have SQL Server 2005 and Visual Studio .NET 2005 installed on my
> developer PC. I installed SQL Server 2005 SP2 last week and installed
> Avast Antivirus this week. What I noticed was that after my reboot, I
> could not get SQL Server to start. In the Surface Area Configuration,
> I was getting error messages in regards to me not having permission to
> start the service.
> So I uninstalled Avast Antivirus (Home Edition btw), and rebooted.
> Alas, SQL Server 2005 was starting up again!
> I use AVG Antivirus (free of course), and was wondering if anybody
> else out there has had similar problems? Is it just Avast?
> Thanks.
>
As this is a developer PC you probably do want to install an antivirus
program, but as Greg says do not scan the database files as SQL Server will
require exclusive access to these files. I would expect user databases to be
marked as suspect if the scan was occurring during start up, but SQL Server
may still start therefore the error message seems slightly spurious. Have yo
u
checked the SQL Server log and the event log for any additional information?
John

Avast Antivirus causing SQL Server 2005 not to start up

I have SQL Server 2005 and Visual Studio .NET 2005 installed on my
developer PC. I installed SQL Server 2005 SP2 last week and installed
Avast Antivirus this week. What I noticed was that after my reboot, I
could not get SQL Server to start. In the Surface Area Configuration,
I was getting error messages in regards to me not having permission to
start the service.
So I uninstalled Avast Antivirus (Home Edition btw), and rebooted.
Alas, SQL Server 2005 was starting up again!
I use AVG Antivirus (free of course), and was wondering if anybody
else out there has had similar problems? Is it just Avast?
Thanks."tofu.captain" <tofu.captain@.gmail.com> wrote in message
news:1176693441.180857.3870@.w1g2000hsg.googlegroups.com...
>I have SQL Server 2005 and Visual Studio .NET 2005 installed on my
> developer PC. I installed SQL Server 2005 SP2 last week and installed
> Avast Antivirus this week. What I noticed was that after my reboot, I
> could not get SQL Server to start. In the Surface Area Configuration,
> I was getting error messages in regards to me not having permission to
> start the service.
> So I uninstalled Avast Antivirus (Home Edition btw), and rebooted.
> Alas, SQL Server 2005 was starting up again!
> I use AVG Antivirus (free of course), and was wondering if anybody
> else out there has had similar problems? Is it just Avast?
Generally suggest not running an AV on a SQL Server. At the very least
suggest telling it to not scan the databases.
> Thanks.
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Hi
"tofu.captain" wrote:
> I have SQL Server 2005 and Visual Studio .NET 2005 installed on my
> developer PC. I installed SQL Server 2005 SP2 last week and installed
> Avast Antivirus this week. What I noticed was that after my reboot, I
> could not get SQL Server to start. In the Surface Area Configuration,
> I was getting error messages in regards to me not having permission to
> start the service.
> So I uninstalled Avast Antivirus (Home Edition btw), and rebooted.
> Alas, SQL Server 2005 was starting up again!
> I use AVG Antivirus (free of course), and was wondering if anybody
> else out there has had similar problems? Is it just Avast?
> Thanks.
>
As this is a developer PC you probably do want to install an antivirus
program, but as Greg says do not scan the database files as SQL Server will
require exclusive access to these files. I would expect user databases to be
marked as suspect if the scan was occurring during start up, but SQL Server
may still start therefore the error message seems slightly spurious. Have you
checked the SQL Server log and the event log for any additional information?
John

Availability of SQL Server 2000

It may be not suitable to ask about SQL 2000 here, but I really want an answer from you experts.
I have my SQL 2000 installed in a Win2000 server, however, the SQL 2000 is not available to my application until I log into a shared folder of the Win2000 or I enable the Guest account of the Win2000.
What is the proper way to let the SQL 2000 available to my application? My SQL 2000 uses SQL Security Mode.
Thanks.If you're using SQL Authentication (also known as mixed mode--it still supports Windows Authentication, too), you can supply a SQL user name and password in your database connection string (or whatever provider you use).

Windows Authentication is by far preferred, because you can use all sorts of Windows domain policies to control access with a lot of flexibility.

-Ryan / Kardax

Sunday, February 12, 2012

AutoStart

Hi,
Installed MSDE desktop (sp3) on XP, however the server does not autostart on
re-booting the machine. In the service manager the server/instance name is
missing after every re-boot. I enter it manually, check the autostart box
and it runs fine, but again after re-boot the server/instance name is lost
again.
I know our work machines are limited in allowing us to edit the registry,
but on a same build machine with full sql svr installed the problem does not
occur.
Any idea?
Cheers, Josh
Hi,
In Control Panel -- Admin tools -- Services -- Select the SQL Server
service.
Double click on the services and make it to automatic and click ok.
Thanks
Hari
SQL Server MVP
"Josh" <joshua.phillips@.notthisbit.blueyonder.co.uk> wrote in message
news:8CF778B9-DED3-48D2-912E-9EEFCC91BA80@.microsoft.com...
> Hi,
> Installed MSDE desktop (sp3) on XP, however the server does not autostart
> on
> re-booting the machine. In the service manager the server/instance name
> is
> missing after every re-boot. I enter it manually, check the autostart box
> and it runs fine, but again after re-boot the server/instance name is lost
> again.
> I know our work machines are limited in allowing us to edit the registry,
> but on a same build machine with full sql svr installed the problem does
> not
> occur.
> Any idea?
> Cheers, Josh
|||Hi,
It is alreday set to auto - the icon in the task bar tray does start, but
the white circle is empty. When I then click on the sql server service
manager, the server / instance name is blank - i.e. it is not remembering the
server / instance name from before the reboot.
Josh
"Hari Prasad" wrote:

> Hi,
> In Control Panel -- Admin tools -- Services -- Select the SQL Server
> service.
> Double click on the services and make it to automatic and click ok.
> Thanks
> Hari
> SQL Server MVP
>
> "Josh" <joshua.phillips@.notthisbit.blueyonder.co.uk> wrote in message
> news:8CF778B9-DED3-48D2-912E-9EEFCC91BA80@.microsoft.com...
>
>
|||hi Josh,
Josh wrote:
> Hi,
> Installed MSDE desktop (sp3) on XP, however the server does not
> autostart on re-booting the machine. In the service manager the
> server/instance name is missing after every re-boot. I enter it
> manually, check the autostart box and it runs fine, but again after
> re-boot the server/instance name is lost again.
> I know our work machines are limited in allowing us to edit the
> registry, but on a same build machine with full sql svr installed the
> problem does not occur.
please have a look at
http://support.microsoft.com/default...b;EN-US;814132
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Thursday, March 29, 2012

Backing Up SQL Serv

Sunday, March 11, 2012

AWE? / Windows 2003 R2 x64 / SQL Server 2000 x86 / 8GB RAM

AWE? / Windows 2003 R2 x64 / SQL Server 2000 x86 / 8GB RAM

AWE, 3GB and SQL Boost

AWE, 3GB and SQL Boost

AWE, 3GB and SQL Boost

Thursday, March 8, 2012

AWE question (Geoff N. Hiten)

AWE question (Geoff N. Hiten)

AWE question (Geoff N. Hiten)

AWE Memory on SQL Server 2000(SP4)

AWE Memory on SQL Server 2000(SP4)

AWE Memory on SQL Server 2000(SP4)

Monday, February 13, 2012

Avast Antivirus causing SQL Server 2005 not to start up

Avast Antivirus causing SQL Server 2005 not to start up

Avast Antivirus causing SQL Server 2005 not to start up

Availability of SQL Server 2000

Sunday, February 12, 2012

AutoStart

Autonumber field

Blog Archive

About Me