Autonumber field: available

Showing posts with label available. Show all posts

Thursday, March 22, 2012

Backing up a DataBase

Hello:
I want to schedule a backup of a Database where a complete backup is done
keeping the Last 10 Complete BackUps Available at all times.
The Backup device file should be something like the DBName+SystemDateTime.
After 10days these backup files will be removed after being copied to
someother location and the whole process of starts all over again from
complete backup1 to complete back10..
Pls suggest some way of doing it.
Thank you.
Hi
The Maintenace Wizard works on this priciple. You define the backup
retention period, and after xx days, the oldest backup is deleted.
If you need to copy the backup off to another server, setup a seperate job,
using XCOPY
Regards
Mike
"Robin Chatterjee" wrote:

> Hello:
> I want to schedule a backup of a Database where a complete backup is done
> keeping the Last 10 Complete BackUps Available at all times.
> The Backup device file should be something like the DBName+SystemDateTime.
> After 10days these backup files will be removed after being copied to
> someother location and the whole process of starts all over again from
> complete backup1 to complete back10..
> Pls suggest some way of doing it.
>
> Thank you.
>

Backing up a DataBase

Hello:
I want to schedule a backup of a Database where a complete backup is done
keeping the Last 10 Complete BackUps Available at all times.
The Backup device file should be something like the DBName+SystemDateTime.
After 10days these backup files will be removed after being copied to
someother location and the whole process of starts all over again from
complete backup1 to complete back10..
Pls suggest some way of doing it.
Thank you.Hi
The Maintenace Wizard works on this priciple. You define the backup
retention period, and after xx days, the oldest backup is deleted.
If you need to copy the backup off to another server, setup a seperate job,
using XCOPY
Regards
Mike
"Robin Chatterjee" wrote:

> Hello:
> I want to schedule a backup of a Database where a complete backup is done
> keeping the Last 10 Complete BackUps Available at all times.
> The Backup device file should be something like the DBName+SystemDateTime.
> After 10days these backup files will be removed after being copied to
> someother location and the whole process of starts all over again from
> complete backup1 to complete back10..
> Pls suggest some way of doing it.
>
> Thank you.
>

Backing up a DataBase

Hello:
I want to schedule a backup of a Database where a complete backup is done
keeping the Last 10 Complete BackUps Available at all times.
The Backup device file should be something like the DBName+SystemDateTime.
After 10days these backup files will be removed after being copied to
someother location and the whole process of starts all over again from
complete backup1 to complete back10..
Pls suggest some way of doing it.
Thank you.Hi
The Maintenace Wizard works on this priciple. You define the backup
retention period, and after xx days, the oldest backup is deleted.
If you need to copy the backup off to another server, setup a seperate job,
using XCOPY
Regards
Mike
"Robin Chatterjee" wrote:
> Hello:
> I want to schedule a backup of a Database where a complete backup is done
> keeping the Last 10 Complete BackUps Available at all times.
> The Backup device file should be something like the DBName+SystemDateTime.
> After 10days these backup files will be removed after being copied to
> someother location and the whole process of starts all over again from
> complete backup1 to complete back10..
> Pls suggest some way of doing it.
>
> Thank you.
>sql

Thursday, March 8, 2012

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 Memory fix (899761) problems

Hi all,
we have some problem installing the path KB899761 (Fix: Not All Memory
is Available When AWE is Enabled on a Computer Running 32-bit Version
of SQL Server 2000 SP4)
Our scenario is:
1 - we added a third node on an existing cluster
2 - The main differences are that the new node have 64 GB of RAM (the
existing ones have only 8 GB) and the "machine" is 64 bit
3 - On this new server we installed windows 2003 (32 bit) with sql
server 2000 SP4 (with "add node" procedure)
4 - To use all the 64 GB of memory we enabled the AWE feature but
we've seen that we could only use 32 GB. For this reason we've found
out that we need the 899761 patch.
Now we tried to install the patch but it seems that it just work on the
old (32 bit) nodes. If we try to install the patch on the new node (we
have the correct instance up and running) we get the following error:
"this machine does not have a product that matches this installation
package"
On the log file we see:
"No products were found which can be serviced by this package"
At the moment we don't know what to try to solve the problem. (maybe
problem with hardware at 64 bit (core 2 duo) and OS at 32 bit ?)
If someone as any idea it would be fantastic ...
Thanks very much in advance.
Kind regards,
Daniel HubeliHi Daniel
You don't say what edition you are using, but I guess from your combination
it can't be Datacenter!
Windows Server 2003, Enterprise Edition supports 32 GB of physical RAM and
Windows Server 2003, Datacenter Edition supports 64 GB of physical RAM
You will not be taking full advantage of your new hardware by running
mismatched products and you would also need to consider if failing over to
the lower spec machines is actually a viable alternative.
John
"daniel.hubeli@.aduno.ch" wrote:

> Hi all,
> we have some problem installing the path KB899761 (Fix: Not All Memory
> is Available When AWE is Enabled on a Computer Running 32-bit Version
> of SQL Server 2000 SP4)
> Our scenario is:
> 1 - we added a third node on an existing cluster
> 2 - The main differences are that the new node have 64 GB of RAM (the
> existing ones have only 8 GB) and the "machine" is 64 bit
> 3 - On this new server we installed windows 2003 (32 bit) with sql
> server 2000 SP4 (with "add node" procedure)
> 4 - To use all the 64 GB of memory we enabled the AWE feature but
> we've seen that we could only use 32 GB. For this reason we've found
> out that we need the 899761 patch.
> Now we tried to install the patch but it seems that it just work on the
> old (32 bit) nodes. If we try to install the patch on the new node (we
> have the correct instance up and running) we get the following error:
> "this machine does not have a product that matches this installation
> package"
> On the log file we see:
> "No products were found which can be serviced by this package"
> At the moment we don't know what to try to solve the problem. (maybe
> problem with hardware at 64 bit (core 2 duo) and OS at 32 bit ?)
> If someone as any idea it would be fantastic ...
> Thanks very much in advance.
> Kind regards,
> Daniel Hubeli
>

AWE Memory fix (899761) problems

Hi all,
we have some problem installing the path KB899761 (Fix: Not All Memory
is Available When AWE is Enabled on a Computer Running 32-bit Version
of SQL Server 2000 SP4)
Our scenario is:
1 - we added a third node on an existing cluster
2 - The main differences are that the new node have 64 GB of RAM (the
existing ones have only 8 GB) and the "machine" is 64 bit
3 - On this new server we installed windows 2003 (32 bit) with sql
server 2000 SP4 (with "add node" procedure)
4 - To use all the 64 GB of memory we enabled the AWE feature but
we've seen that we could only use 32 GB. For this reason we've found
out that we need the 899761 patch.
Now we tried to install the patch but it seems that it just work on the
old (32 bit) nodes. If we try to install the patch on the new node (we
have the correct instance up and running) we get the following error:
"this machine does not have a product that matches this installation
package"
On the log file we see:
"No products were found which can be serviced by this package"
At the moment we don't know what to try to solve the problem. (maybe
problem with hardware at 64 bit (core 2 duo) and OS at 32 bit ?)
If someone as any idea it would be fantastic ...
Thanks very much in advance.
Kind regards,
Daniel Hubeli
Hi Daniel
You don't say what edition you are using, but I guess from your combination
it can't be Datacenter!
Windows Server 2003, Enterprise Edition supports 32 GB of physical RAM and
Windows Server 2003, Datacenter Edition supports 64 GB of physical RAM
You will not be taking full advantage of your new hardware by running
mismatched products and you would also need to consider if failing over to
the lower spec machines is actually a viable alternative.
John
"daniel.hubeli@.aduno.ch" wrote:

> Hi all,
> we have some problem installing the path KB899761 (Fix: Not All Memory
> is Available When AWE is Enabled on a Computer Running 32-bit Version
> of SQL Server 2000 SP4)
> Our scenario is:
> 1 - we added a third node on an existing cluster
> 2 - The main differences are that the new node have 64 GB of RAM (the
> existing ones have only 8 GB) and the "machine" is 64 bit
> 3 - On this new server we installed windows 2003 (32 bit) with sql
> server 2000 SP4 (with "add node" procedure)
> 4 - To use all the 64 GB of memory we enabled the AWE feature but
> we've seen that we could only use 32 GB. For this reason we've found
> out that we need the 899761 patch.
> Now we tried to install the patch but it seems that it just work on the
> old (32 bit) nodes. If we try to install the patch on the new node (we
> have the correct instance up and running) we get the following error:
> "this machine does not have a product that matches this installation
> package"
> On the log file we see:
> "No products were found which can be serviced by this package"
> At the moment we don't know what to try to solve the problem. (maybe
> problem with hardware at 64 bit (core 2 duo) and OS at 32 bit ?)
> If someone as any idea it would be fantastic ...
> Thanks very much in advance.
> Kind regards,
> Daniel Hubeli
>

AWE Memory fix (899761) problems

Hi all,
we have some problem installing the path KB899761 (Fix: Not All Memory
is Available When AWE is Enabled on a Computer Running 32-bit Version
of SQL Server 2000 SP4)
Our scenario is:
1 - we added a third node on an existing cluster
2 - The main differences are that the new node have 64 GB of RAM (the
existing ones have only 8 GB) and the "machine" is 64 bit
3 - On this new server we installed windows 2003 (32 bit) with sql
server 2000 SP4 (with "add node" procedure)
4 - To use all the 64 GB of memory we enabled the AWE feature but
we've seen that we could only use 32 GB. For this reason we've found
out that we need the 899761 patch.
Now we tried to install the patch but it seems that it just work on the
old (32 bit) nodes. If we try to install the patch on the new node (we
have the correct instance up and running) we get the following error:
"this machine does not have a product that matches this installation
package"
On the log file we see:
"No products were found which can be serviced by this package"
At the moment we don't know what to try to solve the problem. (maybe
problem with hardware at 64 bit (core 2 duo) and OS at 32 bit ?)
If someone as any idea it would be fantastic ...
Thanks very much in advance.
Kind regards,
Daniel HubeliHi Daniel
You don't say what edition you are using, but I guess from your combination
it can't be Datacenter!
Windows Server 2003, Enterprise Edition supports 32 GB of physical RAM and
Windows Server 2003, Datacenter Edition supports 64 GB of physical RAM
You will not be taking full advantage of your new hardware by running
mismatched products and you would also need to consider if failing over to
the lower spec machines is actually a viable alternative.
John
"daniel.hubeli@.aduno.ch" wrote:
> Hi all,
> we have some problem installing the path KB899761 (Fix: Not All Memory
> is Available When AWE is Enabled on a Computer Running 32-bit Version
> of SQL Server 2000 SP4)
> Our scenario is:
> 1 - we added a third node on an existing cluster
> 2 - The main differences are that the new node have 64 GB of RAM (the
> existing ones have only 8 GB) and the "machine" is 64 bit
> 3 - On this new server we installed windows 2003 (32 bit) with sql
> server 2000 SP4 (with "add node" procedure)
> 4 - To use all the 64 GB of memory we enabled the AWE feature but
> we've seen that we could only use 32 GB. For this reason we've found
> out that we need the 899761 patch.
> Now we tried to install the patch but it seems that it just work on the
> old (32 bit) nodes. If we try to install the patch on the new node (we
> have the correct instance up and running) we get the following error:
> "this machine does not have a product that matches this installation
> package"
> On the log file we see:
> "No products were found which can be serviced by this package"
> At the moment we don't know what to try to solve the problem. (maybe
> problem with hardware at 64 bit (core 2 duo) and OS at 32 bit ?)
> If someone as any idea it would be fantastic ...
> Thanks very much in advance.
> Kind regards,
> Daniel Hubeli
>

AWE Memory

I am having a problem with SQL using the memory that should be available to it.
I have the following configuration:
Hardware:
CPU: 4 XEON 2.0 GHZ (with HT) - acts like 8
MEMORY: 8 GB RAM
OS: Windows 2003 Advanced Server (PAE is enabled in boot.ini)
SQL: SQL 2000 Enterprise
AWE is enabled
The user account for SQL has Lock Pages in Memory rights
My issue:
I have review the related threads on this site and compared the recommended
settings to my system. I have not found any differences. However the size of
the SQL working memory set will not increase beyond 1.7 GB.
I found a reference on MSDN that stated that when AWE is enabled an entry
"Address Windowing Extension Enabled" is added to the SQL Error Log. I find
no such entry in my log.
I seems as though AWE is not actually running even though all my setting
seem to be ok.
What have I missed?
--
AtvarAtvar,
You also have to set the /3GB switch in boot.ini for SQL Server EE to use
the extra 1GB below the 4GB boundary. Even then it will report something
like 2.7GB used.
See KB 274750, "How to configure memory for more than 2 GB in SQL Server"
http://support.microsoft.com/default.aspx?scid=kb;en-us;274750
Hope this helps,
Ron
--
Ron Talmage
SQL Server MVP
"Atvar" <Atvar@.discussions.microsoft.com> wrote in message
news:741D40E0-A2C4-4529-9F64-56041A96C704@.microsoft.com...
> I am having a problem with SQL using the memory that should be available
to it.
> I have the following configuration:
> Hardware:
> CPU: 4 XEON 2.0 GHZ (with HT) - acts like 8
> MEMORY: 8 GB RAM
> OS: Windows 2003 Advanced Server (PAE is enabled in boot.ini)
> SQL: SQL 2000 Enterprise
> AWE is enabled
> The user account for SQL has Lock Pages in Memory rights
> My issue:
> I have review the related threads on this site and compared the
recommended
> settings to my system. I have not found any differences. However the size
of
> the SQL working memory set will not increase beyond 1.7 GB.
> I found a reference on MSDN that stated that when AWE is enabled an entry
> "Address Windowing Extension Enabled" is added to the SQL Error Log. I
find
> no such entry in my log.
> I seems as though AWE is not actually running even though all my setting
> seem to be ok.
> What have I missed?
> --
> Atvar|||I thought the /3GB switch was not required and was just an option. Is this
not correct?
"Ron Talmage" wrote:
> Atvar,
> You also have to set the /3GB switch in boot.ini for SQL Server EE to use
> the extra 1GB below the 4GB boundary. Even then it will report something
> like 2.7GB used.
> See KB 274750, "How to configure memory for more than 2 GB in SQL Server"
> http://support.microsoft.com/default.aspx?scid=kb;en-us;274750
> Hope this helps,
> Ron
> --
> Ron Talmage
> SQL Server MVP
> "Atvar" <Atvar@.discussions.microsoft.com> wrote in message
> news:741D40E0-A2C4-4529-9F64-56041A96C704@.microsoft.com...
> > I am having a problem with SQL using the memory that should be available
> to it.
> >
> > I have the following configuration:
> >
> > Hardware:
> >
> > CPU: 4 XEON 2.0 GHZ (with HT) - acts like 8
> > MEMORY: 8 GB RAM
> >
> > OS: Windows 2003 Advanced Server (PAE is enabled in boot.ini)
> >
> > SQL: SQL 2000 Enterprise
> >
> > AWE is enabled
> > The user account for SQL has Lock Pages in Memory rights
> >
> > My issue:
> >
> > I have review the related threads on this site and compared the
> recommended
> > settings to my system. I have not found any differences. However the size
> of
> > the SQL working memory set will not increase beyond 1.7 GB.
> >
> > I found a reference on MSDN that stated that when AWE is enabled an entry
> > "Address Windowing Extension Enabled" is added to the SQL Error Log. I
> find
> > no such entry in my log.
> >
> > I seems as though AWE is not actually running even though all my setting
> > seem to be ok.
> >
> > What have I missed?
> >
> > --
> > Atvar
>
>|||It is not required but a good idea in this case. It is not the reason you
are seeing what you say though. I would go back and start from scratch and
ensure you really have Enterprise SQL, WIn2003 Advanced, PAE and AWE turned
on and lock pages in memory for the right account. Verify each, don't just
assume.
--
Andrew J. Kelly SQL MVP
"Atvar" <Atvar@.discussions.microsoft.com> wrote in message
news:97FEA326-585E-460E-AE8D-6910CB4E9345@.microsoft.com...
>I thought the /3GB switch was not required and was just an option. Is this
> not correct?
>
> "Ron Talmage" wrote:
>> Atvar,
>> You also have to set the /3GB switch in boot.ini for SQL Server EE to use
>> the extra 1GB below the 4GB boundary. Even then it will report something
>> like 2.7GB used.
>> See KB 274750, "How to configure memory for more than 2 GB in SQL Server"
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;274750
>> Hope this helps,
>> Ron
>> --
>> Ron Talmage
>> SQL Server MVP
>> "Atvar" <Atvar@.discussions.microsoft.com> wrote in message
>> news:741D40E0-A2C4-4529-9F64-56041A96C704@.microsoft.com...
>> > I am having a problem with SQL using the memory that should be
>> > available
>> to it.
>> >
>> > I have the following configuration:
>> >
>> > Hardware:
>> >
>> > CPU: 4 XEON 2.0 GHZ (with HT) - acts like 8
>> > MEMORY: 8 GB RAM
>> >
>> > OS: Windows 2003 Advanced Server (PAE is enabled in boot.ini)
>> >
>> > SQL: SQL 2000 Enterprise
>> >
>> > AWE is enabled
>> > The user account for SQL has Lock Pages in Memory rights
>> >
>> > My issue:
>> >
>> > I have review the related threads on this site and compared the
>> recommended
>> > settings to my system. I have not found any differences. However the
>> > size
>> of
>> > the SQL working memory set will not increase beyond 1.7 GB.
>> >
>> > I found a reference on MSDN that stated that when AWE is enabled an
>> > entry
>> > "Address Windowing Extension Enabled" is added to the SQL Error Log. I
>> find
>> > no such entry in my log.
>> >
>> > I seems as though AWE is not actually running even though all my
>> > setting
>> > seem to be ok.
>> >
>> > What have I missed?
>> >
>> > --
>> > Atvar
>>|||Thanks for the response.
I did review things as you suggested. The server is running WIn2003
Enterprise (not called advanded in 2003) and the PAE and AWE are set.
However it turn out that the SQL is standard and not Enterprise. This site
uses several SQL servers and the install was done by their IT department.
This server was specified for SQL Enterprise and the license was purchased.
It appears that the wrong license was installed by the IT department. I
think this is my issue as I understand that SQL standard is limited to 2 GB
of memory.
"Andrew J. Kelly" wrote:
> It is not required but a good idea in this case. It is not the reason you
> are seeing what you say though. I would go back and start from scratch and
> ensure you really have Enterprise SQL, WIn2003 Advanced, PAE and AWE turned
> on and lock pages in memory for the right account. Verify each, don't just
> assume.
> --
> Andrew J. Kelly SQL MVP
>
> "Atvar" <Atvar@.discussions.microsoft.com> wrote in message
> news:97FEA326-585E-460E-AE8D-6910CB4E9345@.microsoft.com...
> >I thought the /3GB switch was not required and was just an option. Is this
> > not correct?
> >
> >
> > "Ron Talmage" wrote:
> >
> >> Atvar,
> >>
> >> You also have to set the /3GB switch in boot.ini for SQL Server EE to use
> >> the extra 1GB below the 4GB boundary. Even then it will report something
> >> like 2.7GB used.
> >>
> >> See KB 274750, "How to configure memory for more than 2 GB in SQL Server"
> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;274750
> >>
> >> Hope this helps,
> >> Ron
> >> --
> >> Ron Talmage
> >> SQL Server MVP
> >>
> >> "Atvar" <Atvar@.discussions.microsoft.com> wrote in message
> >> news:741D40E0-A2C4-4529-9F64-56041A96C704@.microsoft.com...
> >> > I am having a problem with SQL using the memory that should be
> >> > available
> >> to it.
> >> >
> >> > I have the following configuration:
> >> >
> >> > Hardware:
> >> >
> >> > CPU: 4 XEON 2.0 GHZ (with HT) - acts like 8
> >> > MEMORY: 8 GB RAM
> >> >
> >> > OS: Windows 2003 Advanced Server (PAE is enabled in boot.ini)
> >> >
> >> > SQL: SQL 2000 Enterprise
> >> >
> >> > AWE is enabled
> >> > The user account for SQL has Lock Pages in Memory rights
> >> >
> >> > My issue:
> >> >
> >> > I have review the related threads on this site and compared the
> >> recommended
> >> > settings to my system. I have not found any differences. However the
> >> > size
> >> of
> >> > the SQL working memory set will not increase beyond 1.7 GB.
> >> >
> >> > I found a reference on MSDN that stated that when AWE is enabled an
> >> > entry
> >> > "Address Windowing Extension Enabled" is added to the SQL Error Log. I
> >> find
> >> > no such entry in my log.
> >> >
> >> > I seems as though AWE is not actually running even though all my
> >> > setting
> >> > seem to be ok.
> >> >
> >> > What have I missed?
> >> >
> >> > --
> >> > Atvar
> >>
> >>
> >>
>
>|||Yes that is it. Standard SQL will only use 2GB regardless of how much the
server has.
--
Andrew J. Kelly SQL MVP
"Atvar" <Atvar@.discussions.microsoft.com> wrote in message
news:433230CD-B250-4CB0-AEAE-9ED0A3F954C8@.microsoft.com...
> Thanks for the response.
> I did review things as you suggested. The server is running WIn2003
> Enterprise (not called advanded in 2003) and the PAE and AWE are set.
> However it turn out that the SQL is standard and not Enterprise. This
> site
> uses several SQL servers and the install was done by their IT department.
> This server was specified for SQL Enterprise and the license was
> purchased.
> It appears that the wrong license was installed by the IT department. I
> think this is my issue as I understand that SQL standard is limited to 2
> GB
> of memory.
>
> "Andrew J. Kelly" wrote:
>> It is not required but a good idea in this case. It is not the reason
>> you
>> are seeing what you say though. I would go back and start from scratch
>> and
>> ensure you really have Enterprise SQL, WIn2003 Advanced, PAE and AWE
>> turned
>> on and lock pages in memory for the right account. Verify each, don't
>> just
>> assume.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Atvar" <Atvar@.discussions.microsoft.com> wrote in message
>> news:97FEA326-585E-460E-AE8D-6910CB4E9345@.microsoft.com...
>> >I thought the /3GB switch was not required and was just an option. Is
>> >this
>> > not correct?
>> >
>> >
>> > "Ron Talmage" wrote:
>> >
>> >> Atvar,
>> >>
>> >> You also have to set the /3GB switch in boot.ini for SQL Server EE to
>> >> use
>> >> the extra 1GB below the 4GB boundary. Even then it will report
>> >> something
>> >> like 2.7GB used.
>> >>
>> >> See KB 274750, "How to configure memory for more than 2 GB in SQL
>> >> Server"
>> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;274750
>> >>
>> >> Hope this helps,
>> >> Ron
>> >> --
>> >> Ron Talmage
>> >> SQL Server MVP
>> >>
>> >> "Atvar" <Atvar@.discussions.microsoft.com> wrote in message
>> >> news:741D40E0-A2C4-4529-9F64-56041A96C704@.microsoft.com...
>> >> > I am having a problem with SQL using the memory that should be
>> >> > available
>> >> to it.
>> >> >
>> >> > I have the following configuration:
>> >> >
>> >> > Hardware:
>> >> >
>> >> > CPU: 4 XEON 2.0 GHZ (with HT) - acts like 8
>> >> > MEMORY: 8 GB RAM
>> >> >
>> >> > OS: Windows 2003 Advanced Server (PAE is enabled in boot.ini)
>> >> >
>> >> > SQL: SQL 2000 Enterprise
>> >> >
>> >> > AWE is enabled
>> >> > The user account for SQL has Lock Pages in Memory rights
>> >> >
>> >> > My issue:
>> >> >
>> >> > I have review the related threads on this site and compared the
>> >> recommended
>> >> > settings to my system. I have not found any differences. However the
>> >> > size
>> >> of
>> >> > the SQL working memory set will not increase beyond 1.7 GB.
>> >> >
>> >> > I found a reference on MSDN that stated that when AWE is enabled an
>> >> > entry
>> >> > "Address Windowing Extension Enabled" is added to the SQL Error Log.
>> >> > I
>> >> find
>> >> > no such entry in my log.
>> >> >
>> >> > I seems as though AWE is not actually running even though all my
>> >> > setting
>> >> > seem to be ok.
>> >> >
>> >> > What have I missed?
>> >> >
>> >> > --
>> >> > Atvar
>> >>
>> >>
>> >>
>>

Monday, February 13, 2012

available values and free text

Hi,
I have a parameter that get his available values from a query.

I want that user will have the option to select from the values list OR to type in his own value.

Is there a way to do that?

Thanks,YOu will have to use two parameters and compose your query to accept either the one or the other value.

HTH; Jens K. Suessmeyer.

http://www.sqlserver2005.de|||Hello Jens,

I was afraid of that :(
I was sure at first that there is a simple solution other then that.

Now it mean that I need to check both parameters and if the user fill them both I need to decide which one to choose and so on...

Any way, It seems that its the only way.

Thanks for your replay,
Roy.

available values and free text

Hi,
I have a parameter that get his available values from a query.

I want that user will have the option to select from the values list OR to type in his own value.

Is there a way to do that?

Thanks,

Hello my friend,

I am assuming that your rdl report is working and the user can select from a drop down list and you just want extra functionality to allow the user to choose their own, which may not be on the list. A way to do this would be to use 2 other parameters. One will be the user's chosen value and the other will be a flag to say whether to use the selected drop down value or what the user entered

SELECT * FROM MyTable WHERE (MyID = @.DropDownListValue AND @.UsingDropDownList = 1)

OR (MyID = @.UserValue AND @.UsingDropDownList = 0)

Kind regards

Scotty

|||

Hi Scotty,

Thank for your replay!

I also thought about useing two parameters but it looked like a really poor idea.

After seeing your answer I got the feeling That Its the only way :(

The problem is that I already have to much parameters and helf the screen is with parameters textBox (since it organized them in two column and I can't do any thing about that),

Thanks for your help,

Roy.

|||

Hello again my friend,

You do not need to use the default parameter screen that the report generates. When you submit the report after choosing your parameters, observe the url it generates. It concatenates your parameters on to the URL. Instead of using the default report screen, you can make your own user-friendly web page where they choose the parameters and then just generate the URL based on their choices and redirect them.

Kind regards

Scotty

available values and free text

Hi,
I have a parameter that get his available values from a query.
I want that user will have the option to select from the values list
OR to type in his own value.
Is there a way to do that?
Thanks,You can have either type in values or drop down you cant have both.
Amarnath
"nicknack" wrote:
> Hi,
> I have a parameter that get his available values from a query.
> I want that user will have the option to select from the values list
> OR to type in his own value.
> Is there a way to do that?
> Thanks,
>|||Yap, Thats what i found out.
Thanks
Amarnath =D7=9B=D7=AA=D7=91:
> You can have either type in values or drop down you cant have both.
> Amarnath
> "nicknack" wrote:
> > Hi,
> > I have a parameter that get his available values from a query.
> >
> > I want that user will have the option to select from the values list
> > OR to type in his own value.
> >
> > Is there a way to do that?
> >
> > Thanks,
> >
> >

Available strategies to upgrade a database schema without downtime

There is a great book on database refactoring that contains a comprehensive set or recipies on how to revise databases that are supposed to be always online and may have various clients that can't be upgraded at the same time. I guess this is a typical case with large databases and I would be surpised if Amazon stops their servers just to move a column from one table to another. The book describes necessary steps for such changes. Basically it's all about creating intermediate database schemas that would be used during transition period.

For example, if we need to move a column from one table to another:

Version 1.
Table A columns: Name, Price
Table B columns: Quantity, Date

Let's say we move Price to table B:

Version 2.
Table A columns: Name
Table B columns: Quantity, Date, Price

The book suggests an intermediate version:

Version 1_2.
Table A columns: Name, Price
Table B columns: Quantity, Date, Price
Additional trigger that will synchronize "Price" columns between A and B.

Version 1_2 can be used by both clients written for version 1 and 2. Software developers don't need to rush their upgrades, transition can last months and include several changes.

This technique requires accuracy in version control management, but looks very good to implement non-interruptible database schema upgrade. I wonder if this is the only option available for data schema upgrade with no downtime. I can't think about anything else - it this how large data warehouses updata their databases?That's a sensible method. Another is to create a view (name,price) and expose it as TableA. With an instead of trigger, you then can update the correct base tables.

available servers in domain

Hi, all
How do I findout available sql servers in the domain?.
Thanks in advancefrom command line type:
osql -L
--
-Vishal
"new" <henry_lin@.yahoo.com> wrote in message
news:#NVEuDsUDHA.1688@.TK2MSFTNGP11.phx.gbl...
> Hi, all
> How do I findout available sql servers in the domain?.
> Thanks in advance
>|||I'm not sure but i doubt it will list the server that is in another domain
though it is trusted.
--
-Vishal
"new" <henry_lin@.yahoo.com> wrote in message
news:u$6FKgsUDHA.2364@.TK2MSFTNGP09.phx.gbl...
> there is another way that I could find out?
> I need check how many sql servers in a trusted domain.
> Do I have to login that domain in order to find out?
> Thanks
> "new" <henry_lin@.yahoo.com> wrote in message
> news:#NVEuDsUDHA.1688@.TK2MSFTNGP11.phx.gbl...
> > Hi, all
> >
> > How do I findout available sql servers in the domain?.
> >
> > Thanks in advance
> >
> >
>|||Small VB function that will return just that.
Private Const SV_TYPE_SQLSERVER As Long = &H4
Private Type SERVER_INFO_100
sv100_platform_id As Long
sv100_name As Long
End Type
Private Declare Function NetApiBufferFree Lib "netapi32" (ByVal Buff As
Long) As Long
Private Declare Function NetServerEnum Lib "netapi32" (ByVal servername
As String, ByVal level As Long, bufptr As Long, ByVal prefmaxlen As
Long, entriesread As Long, totalentries As Long, ByVal servertype As
Long, ByVal Domain As String, resume_handle As Long) As Long
Private Declare Function SysAllocString Lib "oleaut32" (ByVal Source As
Long) As String
Private Declare Function MoveMemory Lib "kernel32" Alias "RtlMoveMemory"
(Dest As Any, Source As Any, ByVal Size As Long) As Long
'Enumerates Servers on a network
Private Function EnumSQLServers() As Variant
Dim lngType As Long
Dim lngSize As Long
Dim lngTotal As Long
Dim hResume As Long
Dim pBuf As Long
Dim arrServers() As SERVER_INFO_100
Dim arrNames As Variant
lngType = SV_TYPE_SQLSERVER
NetServerEnum vbNullString, 100, pBuf, -1, lngSize, lngTotal,
lngType, vbNullString, hResume
ReDim arrServers(lngSize - 1)
MoveMemory arrServers(0), ByVal pBuf, lngSize * Len(arrServers(0))
NetApiBufferFree pBuf
ReDim arrNames(lngSize - 1) As String
For lngTotal = 0 To lngSize - 1
arrNames(lngTotal) =StrConv(SysAllocString(arrServers(lngTotal).sv100_name), vbFromUnicode)
Next
EnumSQLServers = arrNames
End Function
Vishal Parkar wrote:
> I'm not sure but i doubt it will list the server that is in another domain
> though it is trusted.
> --
> -Vishal
> "new" <henry_lin@.yahoo.com> wrote in message
> news:u$6FKgsUDHA.2364@.TK2MSFTNGP09.phx.gbl...
>>there is another way that I could find out?
>>I need check how many sql servers in a trusted domain.
>>Do I have to login that domain in order to find out?
>>Thanks
>>"new" <henry_lin@.yahoo.com> wrote in message
>>news:#NVEuDsUDHA.1688@.TK2MSFTNGP11.phx.gbl...
>>Hi, all
>>How do I findout available sql servers in the domain?.
>>Thanks in advance
>>
>>
>

Available platforms...?

HI,
Can someone please tell me if I can install the SQL Server Client code on and AIX 4.3.3 O/S? When I say client, what I need to do is to install the client code locally on an IBM Infomration Integrator server to enable connectivity to a remote/disparate SQLServer dB.
Your help in this matter will be hugely appreciated.
Regards
Alex.No. You may have to compile your own client with libraries such as freeTDS.
MS was supposedly going to release some SQL client tools for Unix (the rumor
I heard anyway, not meant to create any rumor). But I don't know whether
that is right now.
--
Linchi Shea
linchi_shea@.NOSPAMml.com
"Alex Crockett" <anonymous@.discussions.microsoft.com> wrote in message
news:4521C7EF-9B2E-4CCF-9F6E-D4797C956D15@.microsoft.com...
> HI,
> Can someone please tell me if I can install the SQL Server Client code on
and AIX 4.3.3 O/S? When I say client, what I need to do is to install the
client code locally on an IBM Infomration Integrator server to enable
connectivity to a remote/disparate SQLServer dB.
> Your help in this matter will be hugely appreciated.
> Regards
> Alex.

Available MSSQL Servers during registration ...

Hi all,
Observation: When I use the "Register SQL Server Wizard" I noticed that
there are a number of SQL DB Servers that are not populating the "Available
servers" listbox. Note: this also occurs when I programatically generate a
list of database servers using the ODBC32 API's.
Question: How can I get this list to accurately reflect the databases on my
network? Are there settings on the database server that neet to be changed?
For example, my local development workstation has three databases on it --
the "(local)" instance, and two additional instances ("\DEV" and "\TEST").
The "(local)" instance shows up, but I am not seeing the two other instances
"<COMPUTERNAME>\DEV" and "<COMPUTERNAME>\TEST".
Thoughts?
Thanks!
WadeHi
You may have hide server checked in the SQL Servers TCP/IP setting.
John
"Wade" wrote:
> Hi all,
> Observation: When I use the "Register SQL Server Wizard" I noticed that
> there are a number of SQL DB Servers that are not populating the "Available
> servers" listbox. Note: this also occurs when I programatically generate a
> list of database servers using the ODBC32 API's.
> Question: How can I get this list to accurately reflect the databases on my
> network? Are there settings on the database server that neet to be changed?
> For example, my local development workstation has three databases on it --
> the "(local)" instance, and two additional instances ("\DEV" and "\TEST").
> The "(local)" instance shows up, but I am not seeing the two other instances
> "<COMPUTERNAME>\DEV" and "<COMPUTERNAME>\TEST".
> Thoughts?
> Thanks!
> Wade
>
>|||Hi John,
Thanks for the suggestion. However, I just checked, and all of these DB
servers have TCP/IP and Named Pipes enabled, and the "Hide server" checkbox
has not been checked.
Any other ideas?
Thanks,
Wade
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:EBECB381-89A7-456A-9016-921FDA02413B@.microsoft.com...
> Hi
> You may have hide server checked in the SQL Servers TCP/IP setting.
> John
> "Wade" wrote:
>> Hi all,
>> Observation: When I use the "Register SQL Server Wizard" I noticed that
>> there are a number of SQL DB Servers that are not populating the
>> "Available
>> servers" listbox. Note: this also occurs when I programatically generate
>> a
>> list of database servers using the ODBC32 API's.
>> Question: How can I get this list to accurately reflect the databases on
>> my
>> network? Are there settings on the database server that neet to be
>> changed?
>> For example, my local development workstation has three databases on
>> it --
>> the "(local)" instance, and two additional instances ("\DEV" and
>> "\TEST").
>> The "(local)" instance shows up, but I am not seeing the two other
>> instances
>> "<COMPUTERNAME>\DEV" and "<COMPUTERNAME>\TEST".
>> Thoughts?
>> Thanks!
>> Wade
>>|||The browsing implementation isn't guaranteed to find all servers, quite simply. Type the name.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Wade" <wwegner23NOEMAILhotmail.com> wrote in message
news:%23Dl9gR0pFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi John,
> Thanks for the suggestion. However, I just checked, and all of these DB servers have TCP/IP and
> Named Pipes enabled, and the "Hide server" checkbox has not been checked.
> Any other ideas?
> Thanks,
> Wade
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:EBECB381-89A7-456A-9016-921FDA02413B@.microsoft.com...
>> Hi
>> You may have hide server checked in the SQL Servers TCP/IP setting.
>> John
>> "Wade" wrote:
>> Hi all,
>> Observation: When I use the "Register SQL Server Wizard" I noticed that
>> there are a number of SQL DB Servers that are not populating the "Available
>> servers" listbox. Note: this also occurs when I programatically generate a
>> list of database servers using the ODBC32 API's.
>> Question: How can I get this list to accurately reflect the databases on my
>> network? Are there settings on the database server that neet to be changed?
>> For example, my local development workstation has three databases on it --
>> the "(local)" instance, and two additional instances ("\DEV" and "\TEST").
>> The "(local)" instance shows up, but I am not seeing the two other instances
>> "<COMPUTERNAME>\DEV" and "<COMPUTERNAME>\TEST".
>> Thoughts?
>> Thanks!
>> Wade
>>
>|||Thanks for the info Tibor. Just curious -- is this a definitive answer, or
just your experience? Do you know of any KB article (or anything else) that
discusses this?
Thanks!
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:eFcIbl0pFHA.3572@.TK2MSFTNGP09.phx.gbl...
> The browsing implementation isn't guaranteed to find all servers, quite
> simply. Type the name.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Wade" <wwegner23NOEMAILhotmail.com> wrote in message
> news:%23Dl9gR0pFHA.3064@.TK2MSFTNGP15.phx.gbl...
>> Hi John,
>> Thanks for the suggestion. However, I just checked, and all of these DB
>> servers have TCP/IP and Named Pipes enabled, and the "Hide server"
>> checkbox has not been checked.
>> Any other ideas?
>> Thanks,
>> Wade
>> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
>> news:EBECB381-89A7-456A-9016-921FDA02413B@.microsoft.com...
>> Hi
>> You may have hide server checked in the SQL Servers TCP/IP setting.
>> John
>> "Wade" wrote:
>> Hi all,
>> Observation: When I use the "Register SQL Server Wizard" I noticed that
>> there are a number of SQL DB Servers that are not populating the
>> "Available
>> servers" listbox. Note: this also occurs when I programatically
>> generate a
>> list of database servers using the ODBC32 API's.
>> Question: How can I get this list to accurately reflect the databases
>> on my
>> network? Are there settings on the database server that neet to be
>> changed?
>> For example, my local development workstation has three databases on
>> it --
>> the "(local)" instance, and two additional instances ("\DEV" and
>> "\TEST").
>> The "(local)" instance shows up, but I am not seeing the two other
>> instances
>> "<COMPUTERNAME>\DEV" and "<COMPUTERNAME>\TEST".
>> Thoughts?
>> Thanks!
>> Wade
>>
>>
>|||I think there might be a KN article, should be quick to find out, with a few good keyword to search
for. Also, check www.sqldev.net. There are some examples on calling this browser functionality from
code and there might also be some text on the shortcomings. Below is some text I saved from GertD,
from a previous posting. Come to thing of it, searching the ng archives can be a good idea as well:
There is no way to do return a guaranteed list of install SQL Servers, not
even using the old LAN Manager NetServersEnum looking for SV_TYPE_SQLSERVER
ListAvailableServers using the ODBC function SQLBrowseConnect. This function
performs a discovery broadcast on the network to discover installed SQL
Servers, the SQL Server have to respond on the discovery broadcast, hence
that you will find that not all servers will show up. Some conditions:
1: Only running SQL Servers will show up, however there is a detail (mostly
15 min.) after which the broadcast can be responded by the master browser
services on the network, incase the SQL Server just stopped.
2: On 7.0 the default protocol is Named Pipes which is NetBIOS based, in
2000 it is TCP/IP sockets, hence the broadcast in 7.0 was a NetBIOS
broadcast, which one does not have guaranteed delivery, two most routers are
configured not to pass on NetBIOS broadcast so you only will get subset of
the list of servers, mainly the one in you subnet. For sure the broadcast
does not go beyond or between NT domains. In 2000 this has been changed to a
TCP UDP broadcast.
3: In 7.0, Win9x versions do not respond on the NetBIOS broadcast, hence do
not show up in the list, in 2000 this has been changed to TCP UDP which is
understood by Win9x
4: The response has to be back to the originator within a certain timeout,
otherwise the server named is not included in the list.
Bottom-line, this is never going to return a list of SQL Server that you can
rely on. In 2000 the ability to register a SQL Server in the Active
Directory has been added, this would be a better solution.
That is not what SQL-DMO uses in SQL Server 7.0 and later. This was the case
in 6.5 and previous releases, when only NT was supported.
In 7.0 and later SQL-DMO uses the ODBC function SQLBrowseConnect to retrieve
a list of servers.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Wade" <wwegner23NOEMAILhotmail.com> wrote in message news:Op5cma1pFHA.2076@.TK2MSFTNGP14.phx.gbl...
> Thanks for the info Tibor. Just curious -- is this a definitive answer, or just your experience?
> Do you know of any KB article (or anything else) that discusses this?
> Thanks!
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:eFcIbl0pFHA.3572@.TK2MSFTNGP09.phx.gbl...
>> The browsing implementation isn't guaranteed to find all servers, quite simply. Type the name.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Wade" <wwegner23NOEMAILhotmail.com> wrote in message
>> news:%23Dl9gR0pFHA.3064@.TK2MSFTNGP15.phx.gbl...
>> Hi John,
>> Thanks for the suggestion. However, I just checked, and all of these DB servers have TCP/IP and
>> Named Pipes enabled, and the "Hide server" checkbox has not been checked.
>> Any other ideas?
>> Thanks,
>> Wade
>> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
>> news:EBECB381-89A7-456A-9016-921FDA02413B@.microsoft.com...
>> Hi
>> You may have hide server checked in the SQL Servers TCP/IP setting.
>> John
>> "Wade" wrote:
>> Hi all,
>> Observation: When I use the "Register SQL Server Wizard" I noticed that
>> there are a number of SQL DB Servers that are not populating the "Available
>> servers" listbox. Note: this also occurs when I programatically generate a
>> list of database servers using the ODBC32 API's.
>> Question: How can I get this list to accurately reflect the databases on my
>> network? Are there settings on the database server that neet to be changed?
>> For example, my local development workstation has three databases on it --
>> the "(local)" instance, and two additional instances ("\DEV" and "\TEST").
>> The "(local)" instance shows up, but I am not seeing the two other instances
>> "<COMPUTERNAME>\DEV" and "<COMPUTERNAME>\TEST".
>> Thoughts?
>> Thanks!
>> Wade
>>
>>
>>
>|||Thanks, Tibor.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%239l9QZ7pFHA.620@.TK2MSFTNGP15.phx.gbl...
>I think there might be a KN article, should be quick to find out, with a
>few good keyword to search for. Also, check www.sqldev.net. There are some
>examples on calling this browser functionality from code and there might
>also be some text on the shortcomings. Below is some text I saved from
>GertD, from a previous posting. Come to thing of it, searching the ng
>archives can be a good idea as well:
> There is no way to do return a guaranteed list of install SQL Servers, not
> even using the old LAN Manager NetServersEnum looking for
> SV_TYPE_SQLSERVER
> ListAvailableServers using the ODBC function SQLBrowseConnect. This
> function
> performs a discovery broadcast on the network to discover installed SQL
> Servers, the SQL Server have to respond on the discovery broadcast, hence
> that you will find that not all servers will show up. Some conditions:
> 1: Only running SQL Servers will show up, however there is a detail
> (mostly
> 15 min.) after which the broadcast can be responded by the master browser
> services on the network, incase the SQL Server just stopped.
> 2: On 7.0 the default protocol is Named Pipes which is NetBIOS based, in
> 2000 it is TCP/IP sockets, hence the broadcast in 7.0 was a NetBIOS
> broadcast, which one does not have guaranteed delivery, two most routers
> are
> configured not to pass on NetBIOS broadcast so you only will get subset of
> the list of servers, mainly the one in you subnet. For sure the broadcast
> does not go beyond or between NT domains. In 2000 this has been changed to
> a
> TCP UDP broadcast.
> 3: In 7.0, Win9x versions do not respond on the NetBIOS broadcast, hence
> do
> not show up in the list, in 2000 this has been changed to TCP UDP which is
> understood by Win9x
> 4: The response has to be back to the originator within a certain timeout,
> otherwise the server named is not included in the list.
> Bottom-line, this is never going to return a list of SQL Server that you
> can
> rely on. In 2000 the ability to register a SQL Server in the Active
> Directory has been added, this would be a better solution.
>
> That is not what SQL-DMO uses in SQL Server 7.0 and later. This was the
> case
> in 6.5 and previous releases, when only NT was supported.
> In 7.0 and later SQL-DMO uses the ODBC function SQLBrowseConnect to
> retrieve
> a list of servers.
>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Wade" <wwegner23NOEMAILhotmail.com> wrote in message
> news:Op5cma1pFHA.2076@.TK2MSFTNGP14.phx.gbl...
>> Thanks for the info Tibor. Just curious -- is this a definitive answer,
>> or just your experience? Do you know of any KB article (or anything else)
>> that discusses this?
>> Thanks!
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:eFcIbl0pFHA.3572@.TK2MSFTNGP09.phx.gbl...
>> The browsing implementation isn't guaranteed to find all servers, quite
>> simply. Type the name.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Wade" <wwegner23NOEMAILhotmail.com> wrote in message
>> news:%23Dl9gR0pFHA.3064@.TK2MSFTNGP15.phx.gbl...
>> Hi John,
>> Thanks for the suggestion. However, I just checked, and all of these
>> DB servers have TCP/IP and Named Pipes enabled, and the "Hide server"
>> checkbox has not been checked.
>> Any other ideas?
>> Thanks,
>> Wade
>> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
>> news:EBECB381-89A7-456A-9016-921FDA02413B@.microsoft.com...
>> Hi
>> You may have hide server checked in the SQL Servers TCP/IP setting.
>> John
>> "Wade" wrote:
>> Hi all,
>> Observation: When I use the "Register SQL Server Wizard" I noticed
>> that
>> there are a number of SQL DB Servers that are not populating the
>> "Available
>> servers" listbox. Note: this also occurs when I programatically
>> generate a
>> list of database servers using the ODBC32 API's.
>> Question: How can I get this list to accurately reflect the databases
>> on my
>> network? Are there settings on the database server that neet to be
>> changed?
>> For example, my local development workstation has three databases on
>> it --
>> the "(local)" instance, and two additional instances ("\DEV" and
>> "\TEST").
>> The "(local)" instance shows up, but I am not seeing the two other
>> instances
>> "<COMPUTERNAME>\DEV" and "<COMPUTERNAME>\TEST".
>> Thoughts?
>> Thanks!
>> Wade
>>
>>
>>
>>
>

Thursday, March 22, 2012

Backing up a DataBase

Backing up a DataBase

Backing up a DataBase

Thursday, March 8, 2012

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

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

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

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

AWE Memory fix (899761) problems

AWE Memory fix (899761) problems

AWE Memory fix (899761) problems

AWE Memory

AWE Memory

Monday, February 13, 2012

available values and free text

available values and free text

available values and free text

Available strategies to upgrade a database schema without downtime

available servers in domain

Available platforms...?

Available MSSQL Servers during registration ...

Autonumber field

Blog Archive

About Me