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

awe settings.

SQL2K Ent SP3a Win2k SP3
I've recently enabled awe memory on 2 of our servers.
Everything seems to be going OK, AWE memory counters
are active in performance monitor and the sql serror log
shows awe memory enabled on startup.
My question is, is the above information enough to know that
awe is working correctly? If not, what other things can be looked
at?
TIA.see
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q274750#6
--
BR,
Mark Broadbent mcdba,mcse+i
_________________________
"Stressed" <k@.c.co.uk> wrote in message
news:%23oI0KZzVDHA.2164@.TK2MSFTNGP09.phx.gbl...
> SQL2K Ent SP3a Win2k SP3
> I've recently enabled awe memory on 2 of our servers.
> Everything seems to be going OK, AWE memory counters
> are active in performance monitor and the sql serror log
> shows awe memory enabled on startup.
> My question is, is the above information enough to know that
> awe is working correctly? If not, what other things can be looked
> at?
> TIA.
>
>|||Also, when SQL Server starts you should see a line time in
the event log that says:
"Address Windowing Extensions enabled."
Ron
>--Original Message--
>see
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;Q274750#6
>--
>BR,
>Mark Broadbent mcdba,mcse+i
>_________________________
>"Stressed" <k@.c.co.uk> wrote in message
>news:%23oI0KZzVDHA.2164@.TK2MSFTNGP09.phx.gbl...
>> SQL2K Ent SP3a Win2k SP3
>> I've recently enabled awe memory on 2 of our servers.
>> Everything seems to be going OK, AWE memory counters
>> are active in performance monitor and the sql serror log
>> shows awe memory enabled on startup.
>> My question is, is the above information enough to know
that
>> awe is working correctly? If not, what other things can
be looked
>> at?
>> TIA.
>>
>>
>
>.
>

AWE RAM (SQL 2K not recognizing available AWE RAM)

I have a server with SQL Server 2000 Enterprise Edition
with SP3. The boot.ini is set with /3gb /PAE. The server
system properties list 8GB of RAM. Within SQL Server
sp_configure AWE running is set to 1. SQL Server Memory
properties the Maximum is set to 5.12 GB. But SQL Server
does not recognize AWE setting. I look in the SQL Server
errorlog after the server was rebooted and did not list
AWE memory settings. The Server Performance Monitor
Counter under SQL Server Memory Manager with Target Server
Memory list 2.7GB. This should be 5.12 GB of memory for
SQL Server.
Please help me resolve this problem.
Mike
________________________________________
__________________
[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition
(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINN
T="Microsoft
Windows 2000 Advanced Server" /fastdetect /3gb /PAE
________________________________________
___________________
sp_configure "show advanced options", 1
RECONFIGURE
GO
sp_configure "awe enabled", 1
RECONFIGURE
GO
sp_configure "max server memory", 5120
RECONFIGURE
GO
sp_configure "min server memory", 0
RECONFIGURE
GO
________________________________________
___________________
Output from SP_CONFIGURE
name minimum
maximum config_value run_value
-- -- --
-- --
affinity mask -2147483648
2147483647 0 0
allow updates 0
1 0 0
awe enabled 0
1 1 1
c2 audit mode 0
1 0 0
cost threshold for parallelism 0
32767 5 5
Cross DB Ownership Chaining 0
1 0 0
cursor threshold -1
2147483647 -1 -1
default full-text language 0
2147483647 1033 1033
default language 0
9999 0 0
fill factor (%) 0
100 0 0
index create memory (KB) 704
2147483647 0 0
lightweight pooling 0
1 0 0
locks 5000
2147483647 0 0
max degree of parallelism 0
32 0 0
max server memory (MB) 4
2147483647 5120 5120
max text repl size (B) 0
2147483647 65536 65536
max worker threads 32
32767 255 255
media retention 0
365 0 0
min memory per query (KB) 512
2147483647 1024 1024
min server memory (MB) 0
2147483647 0 0
nested triggers 0
1 1 1
network packet size (B) 512
65536 4096 4096
open objects 0
2147483647 0 0
priority boost 0
1 0 0
query governor cost limit 0
2147483647 0 0
query wait (s) -1
2147483647 -1 -1
recovery interval (min) 0
32767 0 0
remote access 0
1 1 1
remote login timeout (s) 0
2147483647 20 20
remote proc trans 0
1 0 0
remote query timeout (s) 0
2147483647 600 600
scan for startup procs 0
1 1 0
set working set size 0
1 0 0
show advanced options 0
1 1 1
two digit year cutoff 1753
9999 2049 2049
user connections 0
32767 0 0
user options 0
32767 56 56> I have a server with SQL Server 2000 Enterprise Edition
> with SP3. The boot.ini is set with /3gb /PAE. The server
> system properties list 8GB of RAM. Within SQL Server
> sp_configure AWE running is set to 1. SQL Server Memory
> properties the Maximum is set to 5.12 GB. But SQL Server
> does not recognize AWE setting. I look in the SQL Server
> errorlog after the server was rebooted and did not list
> AWE memory settings. The Server Performance Monitor
> Counter under SQL Server Memory Manager with Target Server
> Memory list 2.7GB. This should be 5.12 GB of memory for
> SQL Server.
> Please help me resolve this problem.
> Mike
> ________________________________________
__________________
> [boot loader]
> timeout=10
> default=multi(0)disk(0)rdisk(0)partition
(1)\WINNT
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINN
T="Microsoft
> Windows 2000 Advanced Server" /fastdetect /3gb /PAE
> ________________________________________
___________________
> sp_configure "show advanced options", 1
> RECONFIGURE
> GO
> sp_configure "awe enabled", 1
> RECONFIGURE
> GO
> sp_configure "max server memory", 5120
> RECONFIGURE
> GO
> sp_configure "min server memory", 0
> RECONFIGURE
> GO
> ________________________________________
___________________
> Output from SP_CONFIGURE
> name minimum
> maximum config_value run_value
> -- -- --
> -- --
> affinity mask -2147483648
> 2147483647 0 0
> allow updates 0
> 1 0 0
> awe enabled 0
> 1 1 1
> c2 audit mode 0
> 1 0 0
> cost threshold for parallelism 0
> 32767 5 5
> Cross DB Ownership Chaining 0
> 1 0 0
> cursor threshold -1
> 2147483647 -1 -1
> default full-text language 0
> 2147483647 1033 1033
> default language 0
> 9999 0 0
> fill factor (%) 0
> 100 0 0
> index create memory (KB) 704
> 2147483647 0 0
> lightweight pooling 0
> 1 0 0
> locks 5000
> 2147483647 0 0
> max degree of parallelism 0
> 32 0 0
> max server memory (MB) 4
> 2147483647 5120 5120
> max text repl size (B) 0
> 2147483647 65536 65536
> max worker threads 32
> 32767 255 255
> media retention 0
> 365 0 0
> min memory per query (KB) 512
> 2147483647 1024 1024
> min server memory (MB) 0
> 2147483647 0 0
> nested triggers 0
> 1 1 1
> network packet size (B) 512
> 65536 4096 4096
> open objects 0
> 2147483647 0 0
> priority boost 0
> 1 0 0
> query governor cost limit 0
> 2147483647 0 0
> query wait (s) -1
> 2147483647 -1 -1
> recovery interval (min) 0
> 32767 0 0
> remote access 0
> 1 1 1
> remote login timeout (s) 0
> 2147483647 20 20
> remote proc trans 0
> 1 0 0
> remote query timeout (s) 0
> 2147483647 600 600
> scan for startup procs 0
> 1 1 0
> set working set size 0
> 1 0 0
> show advanced options 0
> 1 1 1
> two digit year cutoff 1753
> 9999 2049 2049
> user connections 0
> 32767 0 0
> user options 0
> 32767 56 56
--
Hi Mike,
Check that the SQL Server startup account has the Lock Pages in Memory
privilege:
http://msdn.microsoft.com/library/d...-us/adminsql/ad
_1_server_1fnd.asp
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.|||I already suggested that...
Andrew J. Kelly SQL MVP
"Eric Crdenas [MSFT]" <ecardena@.online.microsoft.com> wrote in message
news:dAsRybjNEHA.308@.cpmsftngxa10.phx.gbl...
> --
> Hi Mike,
> Check that the SQL Server startup account has the 'Lock Pages in Memory'
> privilege:
>
http://msdn.microsoft.com/library/d...-us/adminsql/ad
> _1_server_1fnd.asp
> --
> Eric Crdenas
> Senior support professional
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>

AWE RAM (SQL 2K not recognizing available AWE RAM)

I have a server with SQL Server 2000 Enterprise Edition
with SP3. The boot.ini is set with /3gb /PAE. The server
system properties list 8GB of RAM. Within SQL Server
sp_configure AWE running is set to 1. SQL Server Memory
properties the Maximum is set to 5.12 GB. But SQL Server
does not recognize AWE setting. I look in the SQL Server
errorlog after the server was rebooted and did not list
AWE memory settings. The Server Performance Monitor
Counter under SQL Server Memory Manager with Target Server
Memory list 2.7GB. This should be 5.12 GB of memory for
SQL Server.
Please help me resolve this problem.
Mike
__________________________________________________ ________
[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microso ft
Windows 2000 Advanced Server" /fastdetect /3gb /PAE
__________________________________________________ _________
sp_configure "show advanced options", 1
RECONFIGURE
GO
sp_configure "awe enabled", 1
RECONFIGURE
GO
sp_configure "max server memory", 5120
RECONFIGURE
GO
sp_configure "min server memory", 0
RECONFIGURE
GO
__________________________________________________ _________
Output from SP_CONFIGURE
name minimum
maximum config_value run_value
-- -- --
-- --
affinity mask -2147483648
2147483647 0 0
allow updates 0
1 0 0
awe enabled 0
1 1 1
c2 audit mode 0
1 0 0
cost threshold for parallelism 0
32767 5 5
Cross DB Ownership Chaining 0
1 0 0
cursor threshold -1
2147483647 -1 -1
default full-text language 0
2147483647 1033 1033
default language 0
9999 0 0
fill factor (%) 0
100 0 0
index create memory (KB) 704
2147483647 0 0
lightweight pooling 0
1 0 0
locks 5000
2147483647 0 0
max degree of parallelism 0
32 0 0
max server memory (MB) 4
2147483647 5120 5120
max text repl size (B) 0
2147483647 65536 65536
max worker threads 32
32767 255 255
media retention 0
365 0 0
min memory per query (KB) 512
2147483647 1024 1024
min server memory (MB) 0
2147483647 0 0
nested triggers 0
1 1 1
network packet size (B) 512
65536 4096 4096
open objects 0
2147483647 0 0
priority boost 0
1 0 0
query governor cost limit 0
2147483647 0 0
query wait (s) -1
2147483647 -1 -1
recovery interval (min) 0
32767 0 0
remote access 0
1 1 1
remote login timeout (s) 0
2147483647 20 20
remote proc trans 0
1 0 0
remote query timeout (s) 0
2147483647 600 600
scan for startup procs 0
1 1 0
set working set size 0
1 0 0
show advanced options 0
1 1 1
two digit year cutoff 1753
9999 2049 2049
user connections 0
32767 0 0
user options 0
32767 56 56
> I have a server with SQL Server 2000 Enterprise Edition
> with SP3. The boot.ini is set with /3gb /PAE. The server
> system properties list 8GB of RAM. Within SQL Server
> sp_configure AWE running is set to 1. SQL Server Memory
> properties the Maximum is set to 5.12 GB. But SQL Server
> does not recognize AWE setting. I look in the SQL Server
> errorlog after the server was rebooted and did not list
> AWE memory settings. The Server Performance Monitor
> Counter under SQL Server Memory Manager with Target Server
> Memory list 2.7GB. This should be 5.12 GB of memory for
> SQL Server.
> Please help me resolve this problem.
> Mike
> __________________________________________________ ________
> [boot loader]
> timeout=10
> default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microso ft
> Windows 2000 Advanced Server" /fastdetect /3gb /PAE
> __________________________________________________ _________
> sp_configure "show advanced options", 1
> RECONFIGURE
> GO
> sp_configure "awe enabled", 1
> RECONFIGURE
> GO
> sp_configure "max server memory", 5120
> RECONFIGURE
> GO
> sp_configure "min server memory", 0
> RECONFIGURE
> GO
> __________________________________________________ _________
> Output from SP_CONFIGURE
> name minimum
> maximum config_value run_value
> -- -- --
> -- --
> affinity mask -2147483648
> 2147483647 0 0
> allow updates 0
> 1 0 0
> awe enabled 0
> 1 1 1
> c2 audit mode 0
> 1 0 0
> cost threshold for parallelism 0
> 32767 5 5
> Cross DB Ownership Chaining 0
> 1 0 0
> cursor threshold -1
> 2147483647 -1 -1
> default full-text language 0
> 2147483647 1033 1033
> default language 0
> 9999 0 0
> fill factor (%) 0
> 100 0 0
> index create memory (KB) 704
> 2147483647 0 0
> lightweight pooling 0
> 1 0 0
> locks 5000
> 2147483647 0 0
> max degree of parallelism 0
> 32 0 0
> max server memory (MB) 4
> 2147483647 5120 5120
> max text repl size (B) 0
> 2147483647 65536 65536
> max worker threads 32
> 32767 255 255
> media retention 0
> 365 0 0
> min memory per query (KB) 512
> 2147483647 1024 1024
> min server memory (MB) 0
> 2147483647 0 0
> nested triggers 0
> 1 1 1
> network packet size (B) 512
> 65536 4096 4096
> open objects 0
> 2147483647 0 0
> priority boost 0
> 1 0 0
> query governor cost limit 0
> 2147483647 0 0
> query wait (s) -1
> 2147483647 -1 -1
> recovery interval (min) 0
> 32767 0 0
> remote access 0
> 1 1 1
> remote login timeout (s) 0
> 2147483647 20 20
> remote proc trans 0
> 1 0 0
> remote query timeout (s) 0
> 2147483647 600 600
> scan for startup procs 0
> 1 1 0
> set working set size 0
> 1 0 0
> show advanced options 0
> 1 1 1
> two digit year cutoff 1753
> 9999 2049 2049
> user connections 0
> 32767 0 0
> user options 0
> 32767 56 56
Hi Mike,
Check that the SQL Server startup account has the Lock Pages in Memory
privilege:
http://msdn.microsoft.com/library/de...us/adminsql/ad
_1_server_1fnd.asp
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
|||I already suggested that...
Andrew J. Kelly SQL MVP
"Eric Crdenas [MSFT]" <ecardena@.online.microsoft.com> wrote in message
news:dAsRybjNEHA.308@.cpmsftngxa10.phx.gbl...
> --
> Hi Mike,
> Check that the SQL Server startup account has the 'Lock Pages in Memory'
> privilege:
>
http://msdn.microsoft.com/library/de...us/adminsql/ad
> _1_server_1fnd.asp
> --
> Eric Crdenas
> Senior support professional
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>

AWE RAM (SQL 2K not recognizing available AWE RAM)

I have a server with SQL Server 2000 Enterprise Edition with SP3.
The boot.ini is set with /3gb /PAE. The server system properties list 8GB of RAM. Within SQL Server sp_configure AWE running is set to 1. SQL Server Memory properties the Maximum is set to 5.12 GB. But SQL Server does not recognize AWE setting.
I look in the SQL Server errorlog after the server was rebooted and did not list AWE memory settings.
The Server Performance Monitor Counter under SQL Server Memory Manager with Target Server Memory list 2.7GB.
This should be 5.12 GB of memory for SQL Server.
Please help me resolve this problem.
Mike
__________________________________________________________
[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
Windows 2000 Advanced Server" /fastdetect /3gb /PAE
___________________________________________________________
sp_configure "show advanced options", 1
RECONFIGURE
GO
sp_configure "awe enabled", 1
RECONFIGURE
GO
sp_configure "max server memory", 5120
RECONFIGURE
GO
sp_configure "min server memory", 0
RECONFIGURE
GO
___________________________________________________________
Output from SP_CONFIGURE
name minimum
maximum config_value run_value
-- -- --
-- --
affinity mask -2147483648
2147483647 0 0
allow updates 0
1 0 0
awe enabled 0
1 1 1
c2 audit mode 0
1 0 0
cost threshold for parallelism 0
32767 5 5
Cross DB Ownership Chaining 0
1 0 0
cursor threshold -1
2147483647 -1 -1
default full-text language 0
2147483647 1033 1033
default language 0
9999 0 0
fill factor (%) 0
100 0 0
index create memory (KB) 704
2147483647 0 0
lightweight pooling 0
1 0 0
locks 5000
2147483647 0 0
max degree of parallelism 0
32 0 0
max server memory (MB) 4
2147483647 5120 5120
max text repl size (B) 0
2147483647 65536 65536
max worker threads 32
32767 255 255
media retention 0
365 0 0
min memory per query (KB) 512
2147483647 1024 1024
min server memory (MB) 0
2147483647 0 0
nested triggers 0
1 1 1
network packet size (B) 512
65536 4096 4096
open objects 0
2147483647 0 0
priority boost 0
1 0 0
query governor cost limit 0
2147483647 0 0
query wait (s) -1
2147483647 -1 -1
recovery interval (min) 0
32767 0 0
remote access 0
1 1 1
remote login timeout (s) 0
2147483647 20 20
remote proc trans 0
1 0 0
remote query timeout (s) 0
2147483647 600 600
scan for startup procs 0
1 1 0
set working set size 0
1 0 0
show advanced options 0
1 1 1
two digit year cutoff 1753
9999 2049 2049
user connections 0
32767 0 0
user options 0
32767 56 56> I have a server with SQL Server 2000 Enterprise Edition
> with SP3. The boot.ini is set with /3gb /PAE. The server
> system properties list 8GB of RAM. Within SQL Server
> sp_configure AWE running is set to 1. SQL Server Memory
> properties the Maximum is set to 5.12 GB. But SQL Server
> does not recognize AWE setting. I look in the SQL Server
> errorlog after the server was rebooted and did not list
> AWE memory settings. The Server Performance Monitor
> Counter under SQL Server Memory Manager with Target Server
> Memory list 2.7GB. This should be 5.12 GB of memory for
> SQL Server.
> Please help me resolve this problem.
> Mike
> __________________________________________________________
> [boot loader]
> timeout=10
> default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
> Windows 2000 Advanced Server" /fastdetect /3gb /PAE
> ___________________________________________________________
> sp_configure "show advanced options", 1
> RECONFIGURE
> GO
> sp_configure "awe enabled", 1
> RECONFIGURE
> GO
> sp_configure "max server memory", 5120
> RECONFIGURE
> GO
> sp_configure "min server memory", 0
> RECONFIGURE
> GO
> ___________________________________________________________
> Output from SP_CONFIGURE
> name minimum
> maximum config_value run_value
> -- -- --
> -- --
> affinity mask -2147483648
> 2147483647 0 0
> allow updates 0
> 1 0 0
> awe enabled 0
> 1 1 1
> c2 audit mode 0
> 1 0 0
> cost threshold for parallelism 0
> 32767 5 5
> Cross DB Ownership Chaining 0
> 1 0 0
> cursor threshold -1
> 2147483647 -1 -1
> default full-text language 0
> 2147483647 1033 1033
> default language 0
> 9999 0 0
> fill factor (%) 0
> 100 0 0
> index create memory (KB) 704
> 2147483647 0 0
> lightweight pooling 0
> 1 0 0
> locks 5000
> 2147483647 0 0
> max degree of parallelism 0
> 32 0 0
> max server memory (MB) 4
> 2147483647 5120 5120
> max text repl size (B) 0
> 2147483647 65536 65536
> max worker threads 32
> 32767 255 255
> media retention 0
> 365 0 0
> min memory per query (KB) 512
> 2147483647 1024 1024
> min server memory (MB) 0
> 2147483647 0 0
> nested triggers 0
> 1 1 1
> network packet size (B) 512
> 65536 4096 4096
> open objects 0
> 2147483647 0 0
> priority boost 0
> 1 0 0
> query governor cost limit 0
> 2147483647 0 0
> query wait (s) -1
> 2147483647 -1 -1
> recovery interval (min) 0
> 32767 0 0
> remote access 0
> 1 1 1
> remote login timeout (s) 0
> 2147483647 20 20
> remote proc trans 0
> 1 0 0
> remote query timeout (s) 0
> 2147483647 600 600
> scan for startup procs 0
> 1 1 0
> set working set size 0
> 1 0 0
> show advanced options 0
> 1 1 1
> two digit year cutoff 1753
> 9999 2049 2049
> user connections 0
> 32767 0 0
> user options 0
> 32767 56 56
--
Hi Mike,
Check that the SQL Server startup account has the ?Lock Pages in Memory?
privilege:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad
_1_server_1fnd.asp
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.|||I already suggested that...
--
Andrew J. Kelly SQL MVP
"Eric Cárdenas [MSFT]" <ecardena@.online.microsoft.com> wrote in message
news:dAsRybjNEHA.308@.cpmsftngxa10.phx.gbl...
> > I have a server with SQL Server 2000 Enterprise Edition
> > with SP3. The boot.ini is set with /3gb /PAE. The server
> > system properties list 8GB of RAM. Within SQL Server
> > sp_configure AWE running is set to 1. SQL Server Memory
> > properties the Maximum is set to 5.12 GB. But SQL Server
> > does not recognize AWE setting. I look in the SQL Server
> > errorlog after the server was rebooted and did not list
> > AWE memory settings. The Server Performance Monitor
> > Counter under SQL Server Memory Manager with Target Server
> > Memory list 2.7GB. This should be 5.12 GB of memory for
> > SQL Server.
> >
> > Please help me resolve this problem.
> >
> > Mike
> >
> > __________________________________________________________
> > [boot loader]
> > timeout=10
> > default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
> > [operating systems]
> > multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
> > Windows 2000 Advanced Server" /fastdetect /3gb /PAE
> > ___________________________________________________________
> > sp_configure "show advanced options", 1
> > RECONFIGURE
> > GO
> > sp_configure "awe enabled", 1
> > RECONFIGURE
> > GO
> > sp_configure "max server memory", 5120
> > RECONFIGURE
> > GO
> > sp_configure "min server memory", 0
> > RECONFIGURE
> > GO
> > ___________________________________________________________
> > Output from SP_CONFIGURE
> > name minimum
> > maximum config_value run_value
> > -- -- --
> > -- --
> > affinity mask -2147483648
> > 2147483647 0 0
> > allow updates 0
> > 1 0 0
> > awe enabled 0
> > 1 1 1
> > c2 audit mode 0
> > 1 0 0
> > cost threshold for parallelism 0
> > 32767 5 5
> > Cross DB Ownership Chaining 0
> > 1 0 0
> > cursor threshold -1
> > 2147483647 -1 -1
> > default full-text language 0
> > 2147483647 1033 1033
> > default language 0
> > 9999 0 0
> > fill factor (%) 0
> > 100 0 0
> > index create memory (KB) 704
> > 2147483647 0 0
> > lightweight pooling 0
> > 1 0 0
> > locks 5000
> > 2147483647 0 0
> > max degree of parallelism 0
> > 32 0 0
> > max server memory (MB) 4
> > 2147483647 5120 5120
> > max text repl size (B) 0
> > 2147483647 65536 65536
> > max worker threads 32
> > 32767 255 255
> > media retention 0
> > 365 0 0
> > min memory per query (KB) 512
> > 2147483647 1024 1024
> > min server memory (MB) 0
> > 2147483647 0 0
> > nested triggers 0
> > 1 1 1
> > network packet size (B) 512
> > 65536 4096 4096
> > open objects 0
> > 2147483647 0 0
> > priority boost 0
> > 1 0 0
> > query governor cost limit 0
> > 2147483647 0 0
> > query wait (s) -1
> > 2147483647 -1 -1
> > recovery interval (min) 0
> > 32767 0 0
> > remote access 0
> > 1 1 1
> > remote login timeout (s) 0
> > 2147483647 20 20
> > remote proc trans 0
> > 1 0 0
> > remote query timeout (s) 0
> > 2147483647 600 600
> > scan for startup procs 0
> > 1 1 0
> > set working set size 0
> > 1 0 0
> > show advanced options 0
> > 1 1 1
> > two digit year cutoff 1753
> > 9999 2049 2049
> > user connections 0
> > 32767 0 0
> > user options 0
> > 32767 56 56
> --
> Hi Mike,
> Check that the SQL Server startup account has the 'Lock Pages in Memory'
> privilege:
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad
> _1_server_1fnd.asp
> --
> Eric Cárdenas
> Senior support professional
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>

AWE RAM (SQL 2K not recognizing available AWE RAM)

I have a server with SQL Server 2000 Enterprise Edition
with SP3. The boot.ini is set with /3gb /PAE. The
server system properties list 8GB of RAM. Within SQL
Server sp_configure AWE running is set to 1. When I look
in the SQL Server error log it tells me that 8 processors
and 2048 MB RAM where detected. SQL Server Memory
properties are set with the Maximum to 5.12 GB. But SQL
Server does not recognize AWE setting. The Server
Performance Monitor Counter under SQL Server Memory
Manager with Target Server Memory list 2.7GB. This
should be 5.12 GB of memory for SQL Server.
Please help me resolve this problem.
Mike
__________________________________________________________
[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
Windows 2000 Advanced Server" /fastdetect /3gb /PAE
__________________________________________________________
_
sp_configure "show advanced options", 1
RECONFIGURE
GO
sp_configure "awe enabled", 1
RECONFIGURE
GO
sp_configure "max server memory", 5120
RECONFIGURE
GO
sp_configure "min server memory", 0
RECONFIGURE
GO
__________________________________________________________
_
Output from SP_CONFIGURE
name minimum
maximum config_value run_value
-- -- --
-
-- --
affinity mask -2147483648
2147483647 0 0
allow updates 0
1 0 0
awe enabled 0
1 1 1
c2 audit mode 0
1 0 0
cost threshold for parallelism 0
32767 5 5
Cross DB Ownership Chaining 0
1 0 0
cursor threshold -1
2147483647 -1 -1
default full-text language 0
2147483647 1033 1033
default language 0
9999 0 0
fill factor (%) 0
100 0 0
index create memory (KB) 704
2147483647 0 0
lightweight pooling 0
1 0 0
locks 5000
2147483647 0 0
max degree of parallelism 0
32 0 0
max server memory (MB) 4
2147483647 5120 5120
max text repl size (B) 0
2147483647 65536 65536
max worker threads 32
32767 255 255
media retention 0
365 0 0
min memory per query (KB) 512
2147483647 1024 1024
min server memory (MB) 0
2147483647 0 0
nested triggers 0
1 1 1
network packet size (B) 512
65536 4096 4096
open objects 0
2147483647 0 0
priority boost 0
1 0 0
query governor cost limit 0
2147483647 0 0
query wait (s) -1
2147483647 -1 -1
recovery interval (min) 0
32767 0 0
remote access 0
1 1 1
remote login timeout (s) 0
2147483647 20 20
remote proc trans 0
1 0 0
remote query timeout (s) 0
2147483647 600 600
scan for startup procs 0
1 1 0
set working set size 0
1 0 0
show advanced options 0
1 1 1
two digit year cutoff 1753
9999 2049 2049
user connections 0
32767 0 0
user options 0
32767 56 56Do you have Lock Pages In Memory set properly? See this:
http://support.microsoft.com/default.aspx?scid=kb;en-us;811891&Product=sql2k
--
Andrew J. Kelly SQL MVP
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:9ede01c4349c$357f8a70$a401280a@.phx.gbl...
> I have a server with SQL Server 2000 Enterprise Edition
> with SP3. The boot.ini is set with /3gb /PAE. The
> server system properties list 8GB of RAM. Within SQL
> Server sp_configure AWE running is set to 1. When I look
> in the SQL Server error log it tells me that 8 processors
> and 2048 MB RAM where detected. SQL Server Memory
> properties are set with the Maximum to 5.12 GB. But SQL
> Server does not recognize AWE setting. The Server
> Performance Monitor Counter under SQL Server Memory
> Manager with Target Server Memory list 2.7GB. This
> should be 5.12 GB of memory for SQL Server.
> Please help me resolve this problem.
> Mike
> __________________________________________________________
> [boot loader]
> timeout=10
> default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
> Windows 2000 Advanced Server" /fastdetect /3gb /PAE
> __________________________________________________________
> _
> sp_configure "show advanced options", 1
> RECONFIGURE
> GO
> sp_configure "awe enabled", 1
> RECONFIGURE
> GO
> sp_configure "max server memory", 5120
> RECONFIGURE
> GO
> sp_configure "min server memory", 0
> RECONFIGURE
> GO
> __________________________________________________________
> _
> Output from SP_CONFIGURE
> name minimum
> maximum config_value run_value
> -- -- --
> -
> -- --
> affinity mask -2147483648
> 2147483647 0 0
> allow updates 0
> 1 0 0
> awe enabled 0
> 1 1 1
> c2 audit mode 0
> 1 0 0
> cost threshold for parallelism 0
> 32767 5 5
> Cross DB Ownership Chaining 0
> 1 0 0
> cursor threshold -1
> 2147483647 -1 -1
> default full-text language 0
> 2147483647 1033 1033
> default language 0
> 9999 0 0
> fill factor (%) 0
> 100 0 0
> index create memory (KB) 704
> 2147483647 0 0
> lightweight pooling 0
> 1 0 0
> locks 5000
> 2147483647 0 0
> max degree of parallelism 0
> 32 0 0
> max server memory (MB) 4
> 2147483647 5120 5120
> max text repl size (B) 0
> 2147483647 65536 65536
> max worker threads 32
> 32767 255 255
> media retention 0
> 365 0 0
> min memory per query (KB) 512
> 2147483647 1024 1024
> min server memory (MB) 0
> 2147483647 0 0
> nested triggers 0
> 1 1 1
> network packet size (B) 512
> 65536 4096 4096
> open objects 0
> 2147483647 0 0
> priority boost 0
> 1 0 0
> query governor cost limit 0
> 2147483647 0 0
> query wait (s) -1
> 2147483647 -1 -1
> recovery interval (min) 0
> 32767 0 0
> remote access 0
> 1 1 1
> remote login timeout (s) 0
> 2147483647 20 20
> remote proc trans 0
> 1 0 0
> remote query timeout (s) 0
> 2147483647 600 600
> scan for startup procs 0
> 1 1 0
> set working set size 0
> 1 0 0
> show advanced options 0
> 1 1 1
> two digit year cutoff 1753
> 9999 2049 2049
> user connections 0
> 32767 0 0
> user options 0
> 32767 56 56
>
>|||The SQL Server service account is listed in the Lock
pages in memory is set the same way three other servers
that work correctly.
Is this server not recognizing this setting?
Please help me with this problem.
Thanks,
Mike
>--Original Message--
>Do you have Lock Pages In Memory set properly? See this:
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;811891&Product=sql2k
>--
>Andrew J. Kelly SQL MVP
>
>"Mike" <anonymous@.discussions.microsoft.com> wrote in
message
>news:9ede01c4349c$357f8a70$a401280a@.phx.gbl...
>> I have a server with SQL Server 2000 Enterprise Edition
>> with SP3. The boot.ini is set with /3gb /PAE. The
>> server system properties list 8GB of RAM. Within SQL
>> Server sp_configure AWE running is set to 1. When I
look
>> in the SQL Server error log it tells me that 8
processors
>> and 2048 MB RAM where detected. SQL Server Memory
>> properties are set with the Maximum to 5.12 GB. But
SQL
>> Server does not recognize AWE setting. The Server
>> Performance Monitor Counter under SQL Server Memory
>> Manager with Target Server Memory list 2.7GB. This
>> should be 5.12 GB of memory for SQL Server.
>> Please help me resolve this problem.
>> Mike
>>
__________________________________________________________
>> [boot loader]
>> timeout=10
>> default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
>> [operating systems]
>> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
>> Windows 2000 Advanced Server" /fastdetect /3gb /PAE
__________________________________________________________
>> _
>> sp_configure "show advanced options", 1
>> RECONFIGURE
>> GO
>> sp_configure "awe enabled", 1
>> RECONFIGURE
>> GO
>> sp_configure "max server memory", 5120
>> RECONFIGURE
>> GO
>> sp_configure "min server memory", 0
>> RECONFIGURE
>> GO
__________________________________________________________
>> _
>> Output from SP_CONFIGURE
>> name minimum
>> maximum config_value run_value
>> -- -- --
--
>> -
>> -- --
>> affinity mask -2147483648
>> 2147483647 0 0
>> allow updates 0
>> 1 0 0
>> awe enabled 0
>> 1 1 1
>> c2 audit mode 0
>> 1 0 0
>> cost threshold for parallelism 0
>> 32767 5 5
>> Cross DB Ownership Chaining 0
>> 1 0 0
>> cursor threshold -1
>> 2147483647 -1 -1
>> default full-text language 0
>> 2147483647 1033 1033
>> default language 0
>> 9999 0 0
>> fill factor (%) 0
>> 100 0 0
>> index create memory (KB) 704
>> 2147483647 0 0
>> lightweight pooling 0
>> 1 0 0
>> locks 5000
>> 2147483647 0 0
>> max degree of parallelism 0
>> 32 0 0
>> max server memory (MB) 4
>> 2147483647 5120 5120
>> max text repl size (B) 0
>> 2147483647 65536 65536
>> max worker threads 32
>> 32767 255 255
>> media retention 0
>> 365 0 0
>> min memory per query (KB) 512
>> 2147483647 1024 1024
>> min server memory (MB) 0
>> 2147483647 0 0
>> nested triggers 0
>> 1 1 1
>> network packet size (B) 512
>> 65536 4096 4096
>> open objects 0
>> 2147483647 0 0
>> priority boost 0
>> 1 0 0
>> query governor cost limit 0
>> 2147483647 0 0
>> query wait (s) -1
>> 2147483647 -1 -1
>> recovery interval (min) 0
>> 32767 0 0
>> remote access 0
>> 1 1 1
>> remote login timeout (s) 0
>> 2147483647 20 20
>> remote proc trans 0
>> 1 0 0
>> remote query timeout (s) 0
>> 2147483647 600 600
>> scan for startup procs 0
>> 1 1 0
>> set working set size 0
>> 1 0 0
>> show advanced options 0
>> 1 1 1
>> two digit year cutoff 1753
>> 9999 2049 2049
>> user connections 0
>> 32767 0 0
>> user options 0
>> 32767 56 56
>>
>>
>
>.
>|||According to the results of sp_configure your run value is still set to 0
for AWE. Did you restart the server? And are you absolutely sure you have
SQL EE? What does xp_msver show?
--
Andrew J. Kelly SQL MVP
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:a04c01c434f9$3dde5ae0$a401280a@.phx.gbl...
> The SQL Server service account is listed in the Lock
> pages in memory is set the same way three other servers
> that work correctly.
> Is this server not recognizing this setting?
> Please help me with this problem.
> Thanks,
> Mike
>
> >--Original Message--
> >Do you have Lock Pages In Memory set properly? See this:
> >http://support.microsoft.com/default.aspx?scid=kb;en-
> us;811891&Product=sql2k
> >
> >--
> >Andrew J. Kelly SQL MVP
> >
> >
> >"Mike" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:9ede01c4349c$357f8a70$a401280a@.phx.gbl...
> >>
> >> I have a server with SQL Server 2000 Enterprise Edition
> >> with SP3. The boot.ini is set with /3gb /PAE. The
> >> server system properties list 8GB of RAM. Within SQL
> >> Server sp_configure AWE running is set to 1. When I
> look
> >> in the SQL Server error log it tells me that 8
> processors
> >> and 2048 MB RAM where detected. SQL Server Memory
> >> properties are set with the Maximum to 5.12 GB. But
> SQL
> >> Server does not recognize AWE setting. The Server
> >> Performance Monitor Counter under SQL Server Memory
> >> Manager with Target Server Memory list 2.7GB. This
> >> should be 5.12 GB of memory for SQL Server.
> >>
> >> Please help me resolve this problem.
> >>
> >> Mike
> >>
> >>
> __________________________________________________________
> >> [boot loader]
> >> timeout=10
> >> default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
> >> [operating systems]
> >> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
> >> Windows 2000 Advanced Server" /fastdetect /3gb /PAE
> >>
> __________________________________________________________
> >> _
> >> sp_configure "show advanced options", 1
> >> RECONFIGURE
> >> GO
> >> sp_configure "awe enabled", 1
> >> RECONFIGURE
> >> GO
> >> sp_configure "max server memory", 5120
> >> RECONFIGURE
> >> GO
> >> sp_configure "min server memory", 0
> >> RECONFIGURE
> >> GO
> >>
> __________________________________________________________
> >> _
> >> Output from SP_CONFIGURE
> >> name minimum
> >> maximum config_value run_value
> >> -- -- --
> --
> >> -
> >> -- --
> >> affinity mask -2147483648
> >> 2147483647 0 0
> >> allow updates 0
> >> 1 0 0
> >> awe enabled 0
> >> 1 1 1
> >> c2 audit mode 0
> >> 1 0 0
> >> cost threshold for parallelism 0
> >> 32767 5 5
> >> Cross DB Ownership Chaining 0
> >> 1 0 0
> >> cursor threshold -1
> >> 2147483647 -1 -1
> >> default full-text language 0
> >> 2147483647 1033 1033
> >> default language 0
> >> 9999 0 0
> >> fill factor (%) 0
> >> 100 0 0
> >> index create memory (KB) 704
> >> 2147483647 0 0
> >> lightweight pooling 0
> >> 1 0 0
> >> locks 5000
> >> 2147483647 0 0
> >> max degree of parallelism 0
> >> 32 0 0
> >> max server memory (MB) 4
> >> 2147483647 5120 5120
> >> max text repl size (B) 0
> >> 2147483647 65536 65536
> >> max worker threads 32
> >> 32767 255 255
> >> media retention 0
> >> 365 0 0
> >> min memory per query (KB) 512
> >> 2147483647 1024 1024
> >> min server memory (MB) 0
> >> 2147483647 0 0
> >> nested triggers 0
> >> 1 1 1
> >> network packet size (B) 512
> >> 65536 4096 4096
> >> open objects 0
> >> 2147483647 0 0
> >> priority boost 0
> >> 1 0 0
> >> query governor cost limit 0
> >> 2147483647 0 0
> >> query wait (s) -1
> >> 2147483647 -1 -1
> >> recovery interval (min) 0
> >> 32767 0 0
> >> remote access 0
> >> 1 1 1
> >> remote login timeout (s) 0
> >> 2147483647 20 20
> >> remote proc trans 0
> >> 1 0 0
> >> remote query timeout (s) 0
> >> 2147483647 600 600
> >> scan for startup procs 0
> >> 1 1 0
> >> set working set size 0
> >> 1 0 0
> >> show advanced options 0
> >> 1 1 1
> >> two digit year cutoff 1753
> >> 9999 2049 2049
> >> user connections 0
> >> 32767 0 0
> >> user options 0
> >> 32767 56 56
> >>
> >>
> >>
> >>
> >
> >
> >.
> >

AWE and set working set size

Hello everybody!
System description:
OS: Windows Server 2003 Enterprise Edition SP1
RAM: 16 Gb
SQL: SQL Server 2000 Enterprise Edition SP3
SQL Server has "awe enabled"=1 and "set working set size"=1 at the same time.
"Max server memory" is limited by 12 Gb. SQLServer:MemoryManager:Total
Server Memory counter shows that SQL Server consumes all of the 12 Gb memory.
Allmost every day the client receives ODBC error 1222 (lock timeout) even if
only one user is connected to the database.
BOL says that if "awe enabled"=1 memory is not swapped out by default.
www.microsoft.com says that if you change "set working set size" from its
default value it may involve 844 and 845 errors (page latch timeout).
So the questions are:
1. Can two simulaneously enabled options ("awe enabled" and "set working set
size") result in such conflict?
2. Can enabling set working set size result in ODBC error 1222?
Thank youI don't know if that configuration will cause that error but I doubt it.
There is no reason to have SET Working Set Size set to 1 when you have AWE
since AWE in 2000 is not dynamic to begin with. AWE also allocates all the
memory up to the Max memory setting on startup. I would turn it off and see
if the errors go away and I see no need to have in on anyway.
--
Andrew J. Kelly SQL MVP
"RDBSAdmin" <RDBSAdmin@.discussions.microsoft.com> wrote in message
news:CFCDD61D-ACE4-4C25-ABF1-50395C763B8E@.microsoft.com...
> Hello everybody!
> System description:
> OS: Windows Server 2003 Enterprise Edition SP1
> RAM: 16 Gb
> SQL: SQL Server 2000 Enterprise Edition SP3
> SQL Server has "awe enabled"=1 and "set working set size"=1 at the same
> time.
> "Max server memory" is limited by 12 Gb. SQLServer:MemoryManager:Total
> Server Memory counter shows that SQL Server consumes all of the 12 Gb
> memory.
> Allmost every day the client receives ODBC error 1222 (lock timeout) even
> if
> only one user is connected to the database.
> BOL says that if "awe enabled"=1 memory is not swapped out by default.
> www.microsoft.com says that if you change "set working set size" from its
> default value it may involve 844 and 845 errors (page latch timeout).
> So the questions are:
> 1. Can two simulaneously enabled options ("awe enabled" and "set working
> set
> size") result in such conflict?
> 2. Can enabling set working set size result in ODBC error 1222?
> Thank you
>|||Thank you, Mr.Kelly. Before I read you answer I had decided to act by trial
and error and I advice to turn "working set size" off. My client informed me
that the error did not disappear but it got less frequent.|||The Lock Timeout setting is infinite by default in SQL Server. IF they are
getting this message that means someone somewhere changed the setting. I
would look for any code that has SET LOCK_TIMEOUT in it and find out why and
what value they set it to.
--
Andrew J. Kelly SQL MVP
"RDBSAdmin" <RDBSAdmin@.discussions.microsoft.com> wrote in message
news:69717477-0287-4FB8-9F65-96168F25F2BB@.microsoft.com...
> Thank you, Mr.Kelly. Before I read you answer I had decided to act by
> trial
> and error and I advice to turn "working set size" off. My client informed
> me
> that the error did not disappear but it got less frequent.|||Yes, I see, but can only one user working with the server lock himself? I
mean there are situations when only one user works with the database but the
error occurs all the same.
"Andrew J. Kelly" wrote:
> The Lock Timeout setting is infinite by default in SQL Server. IF they are
> getting this message that means someone somewhere changed the setting. I
> would look for any code that has SET LOCK_TIMEOUT in it and find out why and
> what value they set it to.
> --
> Andrew J. Kelly SQL MVP
>
> "RDBSAdmin" <RDBSAdmin@.discussions.microsoft.com> wrote in message
> news:69717477-0287-4FB8-9F65-96168F25F2BB@.microsoft.com...
> > Thank you, Mr.Kelly. Before I read you answer I had decided to act by
> > trial
> > and error and I advice to turn "working set size" off. My client informed
> > me
> > that the error did not disappear but it got less frequent.
>
>|||Sure. If the user is trying to get an exclusive table lock there are lots of
things that can prevent him from getting one. I think you need to see the
code and why they are setting this and under what conditions it is
happening.
--
Andrew J. Kelly SQL MVP
"RDBSAdmin" <RDBSAdmin@.discussions.microsoft.com> wrote in message
news:057E64D8-ED9F-4442-9623-FECE3BDB865E@.microsoft.com...
> Yes, I see, but can only one user working with the server lock himself? I
> mean there are situations when only one user works with the database but
> the
> error occurs all the same.
> "Andrew J. Kelly" wrote:
>> The Lock Timeout setting is infinite by default in SQL Server. IF they
>> are
>> getting this message that means someone somewhere changed the setting. I
>> would look for any code that has SET LOCK_TIMEOUT in it and find out why
>> and
>> what value they set it to.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "RDBSAdmin" <RDBSAdmin@.discussions.microsoft.com> wrote in message
>> news:69717477-0287-4FB8-9F65-96168F25F2BB@.microsoft.com...
>> > Thank you, Mr.Kelly. Before I read you answer I had decided to act by
>> > trial
>> > and error and I advice to turn "working set size" off. My client
>> > informed
>> > me
>> > that the error did not disappear but it got less frequent.
>>|||There is a general interface setting which allow users to set time-out (via
the setting the code receives time interval for SET LOCK_TIMEOUT statement).
The only thing I'm going to recommend is to increase the value. Thank you,
Mr.Kelly, you have been very helpful.
"Andrew J. Kelly" wrote:
> Sure. If the user is trying to get an exclusive table lock there are lots of
> things that can prevent him from getting one. I think you need to see the
> code and why they are setting this and under what conditions it is
> happening.
> --
> Andrew J. Kelly SQL MVP
>
> "RDBSAdmin" <RDBSAdmin@.discussions.microsoft.com> wrote in message
> news:057E64D8-ED9F-4442-9623-FECE3BDB865E@.microsoft.com...
> > Yes, I see, but can only one user working with the server lock himself? I
> > mean there are situations when only one user works with the database but
> > the
> > error occurs all the same.
> >
> > "Andrew J. Kelly" wrote:
> >
> >> The Lock Timeout setting is infinite by default in SQL Server. IF they
> >> are
> >> getting this message that means someone somewhere changed the setting. I
> >> would look for any code that has SET LOCK_TIMEOUT in it and find out why
> >> and
> >> what value they set it to.
> >>
> >> --
> >> Andrew J. Kelly SQL MVP
> >>
> >>
> >> "RDBSAdmin" <RDBSAdmin@.discussions.microsoft.com> wrote in message
> >> news:69717477-0287-4FB8-9F65-96168F25F2BB@.microsoft.com...
> >> > Thank you, Mr.Kelly. Before I read you answer I had decided to act by
> >> > trial
> >> > and error and I advice to turn "working set size" off. My client
> >> > informed
> >> > me
> >> > that the error did not disappear but it got less frequent.
> >>
> >>
> >>
>
>

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