SQL SQLExpress: setup

Showing posts with label setup. Show all posts

Thursday, March 22, 2012

Turning Off TCP/IP Client Has No Effect ?

Hi Everyone,
I was doing some testing with client configuration and I'm seeing
something I don't understand. Let me explain the setup.
My setup involves a single machine running "SQL Server Express 2005".
As you probably know, SSE includes the "SQL Server Native Client". I
run the "SQL Server Configuration Manager" and under the "SQL Native
Client Configuration" | "Client Protocols" node, I disable TCP/IP. My
understanding is that this should prevent clients on this machine from
using TCP/IP to connect to any SQL Server instance. Does this sound
right so far?
Well, when I run SQLCMD (specifying "tcp:" as the protocol) I am still
able to connect to the instance on the local machine.
In other words, I have TCP/IP disabled as a client protocol, yet I am
still able to successfully connect to an instance using SQLCMD with a
command line like this:
SQLCMD -S tcp:.\TEST_01 -d AdventureWorks
Now, it's my understanding that SQLCMD relies upon the "SQL Server
Native Client". And since I've (supposedly) configured the "SQL Server
Native Client" *NOT* to allow TCP/IP connections, the above SQLCMD
connection should not work, yet it does.
What am I missing here?
AlanDid you stop and restart the service after disabling TCP/IP
protocol? The settings won't take effect until after you
restart the service.
-Sue
On Mon, 10 Apr 2006 01:38:29 -0500, "Alan Foxmore"
<AFoxmore@.yahoo.com> wrote:

>Hi Everyone,
>I was doing some testing with client configuration and I'm seeing
>something I don't understand. Let me explain the setup.
>My setup involves a single machine running "SQL Server Express 2005".
>As you probably know, SSE includes the "SQL Server Native Client". I
>run the "SQL Server Configuration Manager" and under the "SQL Native
>Client Configuration" | "Client Protocols" node, I disable TCP/IP. My
>understanding is that this should prevent clients on this machine from
>using TCP/IP to connect to any SQL Server instance. Does this sound
>right so far?
>Well, when I run SQLCMD (specifying "tcp:" as the protocol) I am still
>able to connect to the instance on the local machine.
>In other words, I have TCP/IP disabled as a client protocol, yet I am
>still able to successfully connect to an instance using SQLCMD with a
>command line like this:
>SQLCMD -S tcp:.\TEST_01 -d AdventureWorks
>Now, it's my understanding that SQLCMD relies upon the "SQL Server
>Native Client". And since I've (supposedly) configured the "SQL Server
>Native Client" *NOT* to allow TCP/IP connections, the above SQLCMD
>connection should not work, yet it does.
>What am I missing here?

Tuesday, March 20, 2012

/L*v C:\temp\logfile

Hi!
I found that using /L*v with the setup procedure creates a verbose log
file. Is there any way to add a verbose log file to an existing database?
Stefan
hi Stefan,
"Stefan M. Huber" <looseleaf@.gmx.net> ha scritto nel messaggio
news:opsfqz6rois9ddfw@.news.individual.de
> Hi!
> I found that using /L*v with the setup procedure creates a verbose
> log file. Is there any way to add a verbose log file to an existing
> database?
> Stefan
/L*v is a setup parameter, which enables the setup logging features...
I do not understand your requirements regarding "add a verbose log file to
an existing database"...
all SQL Server databases do have a transaction log file at least, and the
logging mode is dependent to the recovery setting, as described in
http://msdn.microsoft.com/library/de...kprst_6rqr.asp
...
can you please elaborate your requirements?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||On Tue, 12 Oct 2004 11:05:25 +0200, Andrea Montanari
<andrea.sqlDMO@.virgilio.it> wrote:

> hi Stefan,
> "Stefan M. Huber" <looseleaf@.gmx.net> ha scritto nel messaggio
> news:opsfqz6rois9ddfw@.news.individual.de
> /L*v is a setup parameter, which enables the setup logging features...
> I do not understand your requirements regarding "add a verbose log file
> to an existing database"...
> all SQL Server databases do have a transaction log file at least, and the
> logging mode is dependent to the recovery setting, as described in
> http://msdn.microsoft.com/library/de...kprst_6rqr.asp
> ..
> can you please elaborate your requirements?
I am having troubles when connecting to MSDE 1.0 after installing XP SP2:
The inital connection takes an eternity (10 seconds on lightning fast
machines, up to 90 seconds on my older working machine). In this time,
sqlsvr.exe causes 100% processor load and a lot of I/O stress. I'd simply
like to find out what is going on.
After the initial connection lag, operation continues normally.
We connect through Delphi 5 using ADO.
any pointers appreciated (upgrading to D7 is not an option; it's not my
decision)
Stefan
|||hi Stefan,
"Stefan M. Huber" <looseleaf@.gmx.net> ha scritto nel messaggio
news:opsfq3c3uks9ddfw@.news.individual.de
> I am having troubles when connecting to MSDE 1.0 after installing XP
> SP2: The inital connection takes an eternity (10 seconds on lightning
> fast machines, up to 90 seconds on my older working machine). In this
> time, sqlsvr.exe causes 100% processor load and a lot of I/O stress.
> I'd simply like to find out what is going on.
> After the initial connection lag, operation continues normally.
> We connect through Delphi 5 using ADO.
> any pointers appreciated (upgrading to D7 is not an option; it's not
> my decision)
> Stefan
XP sp2 causes a lot of connection issues, see
http://www.michna.com/kb/WxSP2.htm for instance...
for related SQL Server issues please have a look at
http://support.microsoft.com/default.aspx?kbid=841249
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||On Tue, 12 Oct 2004 13:04:27 +0200, Andrea Montanari
<andrea.sqlDMO@.virgilio.it> wrote:

> XP sp2 causes a lot of connection issues, see
> http://www.michna.com/kb/WxSP2.htm for instance...
> for related SQL Server issues please have a look at
> http://support.microsoft.com/default.aspx?kbid=841249
Thanks for the pointers, Andrea. We've gone through the second one
already; I'll double check if we missed something there.
Do you think that an upgrade to MSDE 2000 would cure some issues?
Stefan, off reading
|||hi Stefan,
"Stefan M. Huber" <looseleaf@.gmx.net> ha scritto nel messaggio
news:opsfq89i1ws9ddfw@.news.individual.de
> ..
> Thanks for the pointers, Andrea. We've gone through the second one
> already; I'll double check if we missed something there.
> Do you think that an upgrade to MSDE 2000 would cure some issues?
> Stefan, off reading
actually not, but MSDE 2000 can be worth upgrading becouse several
improvements in the database engine...
I only installed a Virtual Machine of WinXP sp 2 but had (fortunately) no
related issue to connectivity..
opened the TCP port required for network connections and enlisted a range of
subnet IP addresses... all is ok..
... and I hope to be that lucky when upgrading the real physical machine
=;-D
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||On Tue, 12 Oct 2004 15:39:23 +0200, Andrea Montanari
<andrea.sqlDMO@.virgilio.it> wrote:

> hi Stefan,
> "Stefan M. Huber" <looseleaf@.gmx.net> ha scritto nel messaggio
> news:opsfq89i1ws9ddfw@.news.individual.de
> actually not, but MSDE 2000 can be worth upgrading becouse several
> improvements in the database engine...
Yes; as long as we can easily handle upgrading issues, like the password
in all our connection strings.

> I only installed a Virtual Machine of WinXP sp 2 but had (fortunately) no
> related issue to connectivity..
> opened the TCP port required for network connections and enlisted a
> range of subnet IP addresses... all is ok..
> ... and I hope to be that lucky when upgrading the real physical machine
> =;-D
I'd rather set up a complete testing machine beforehand

Good luck and thanks,
Stefan

/3Gb option set, but SQL Server use only 1.7Gb....

Hi,
I have setup the /3Gb option in the boot.ini file because my server has 4Gb
of RAM.
But SQL Server still use only 1.7Gb.
on another server, there is no problems, the same parameters and SQL Server
use more then 2Gb of memory!!!
there is anything missing ?
what can I check?
thanks.
Jerome.Which OS version and edition and SQL Server edition are you using?
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright © SQLDev.Net 1991-2005 All rights reserved.
"Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
news:uaW1M4HaFHA.2212@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I have setup the /3Gb option in the boot.ini file because my server has
> 4Gb of RAM.
> But SQL Server still use only 1.7Gb.
> on another server, there is no problems, the same parameters and SQL
> Server use more then 2Gb of memory!!!
> there is anything missing ?
> what can I check?
> thanks.
> Jerome.
>|||Jéjé wrote:
> Hi,
> I have setup the /3Gb option in the boot.ini file because my server
> has 4Gb of RAM.
> But SQL Server still use only 1.7Gb.
> on another server, there is no problems, the same parameters and SQL
> Server use more then 2Gb of memory!!!
> there is anything missing ?
> what can I check?
> thanks.
> Jerome.
Are you running SQL 2000 Service Pack 4? If so, there's a known issue
with AWE that is going to be addressed with a hotfix in the next week or
two.
--
David Gugick
Quest Software
www.imceda.com
www.quest.com|||"Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
news:uaW1M4HaFHA.2212@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I have setup the /3Gb option in the boot.ini file because my server has
> 4Gb of RAM.
> But SQL Server still use only 1.7Gb.
> on another server, there is no problems, the same parameters and SQL
> Server use more then 2Gb of memory!!!
> there is anything missing ?
> what can I check?
Use /pae in boot.ini and enable awe in SQL Server, then your SQL should be
able to consume ca. 3.75 GB of RAM (W2K AS + SQL EE SP3)
Regards
Wojtek|||Yes, SP4 installed
on a Win 2003 Enterprise edition server
AWE is NOT enable on the server.
For a 4Gb system what is the best option?
/3Gb
/3Gb + AWE
/PAE
/PAE + AWE
/3Gb /PAE
/3Gb /PAE + AWE
?
"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:eYe9KLIaFHA.616@.TK2MSFTNGP12.phx.gbl...
> Jéjé wrote:
>> Hi,
>> I have setup the /3Gb option in the boot.ini file because my server
>> has 4Gb of RAM.
>> But SQL Server still use only 1.7Gb.
>> on another server, there is no problems, the same parameters and SQL
>> Server use more then 2Gb of memory!!!
>> there is anything missing ?
>> what can I check?
>> thanks.
>> Jerome.
> Are you running SQL 2000 Service Pack 4? If so, there's a known issue with
> AWE that is going to be addressed with a hotfix in the next week or two.
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com|||"Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
news:uJz3PVKaFHA.612@.TK2MSFTNGP12.phx.gbl...
> Yes, SP4 installed
> on a Win 2003 Enterprise edition server
> AWE is NOT enable on the server.
> For a 4Gb system what is the best option?
> /3Gb
> /3Gb + AWE
> /PAE
> /PAE + AWE
> /3Gb /PAE
> /3Gb /PAE + AWE
> ?
/3Gb /PAE + AWE
But AFAIK not with SP4... SP4 has some issue with /pae and AWE.
Regards
Wojtek|||You still need SQL Enterprise Edition to use more than 2GB. It sounds like
you are using Standard Edition of SQL Server. What does @.@.Version show?
--
Andrew J. Kelly SQL MVP
"Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
news:uJz3PVKaFHA.612@.TK2MSFTNGP12.phx.gbl...
> Yes, SP4 installed
> on a Win 2003 Enterprise edition server
> AWE is NOT enable on the server.
> For a 4Gb system what is the best option?
> /3Gb
> /3Gb + AWE
> /PAE
> /PAE + AWE
> /3Gb /PAE
> /3Gb /PAE + AWE
> ?
>
> "David Gugick" <david.gugick-nospam@.quest.com> wrote in message
> news:eYe9KLIaFHA.616@.TK2MSFTNGP12.phx.gbl...
>> Jéjé wrote:
>> Hi,
>> I have setup the /3Gb option in the boot.ini file because my server
>> has 4Gb of RAM.
>> But SQL Server still use only 1.7Gb.
>> on another server, there is no problems, the same parameters and SQL
>> Server use more then 2Gb of memory!!!
>> there is anything missing ?
>> what can I check?
>> thanks.
>> Jerome.
>> Are you running SQL 2000 Service Pack 4? If so, there's a known issue
>> with AWE that is going to be addressed with a hotfix in the next week or
>> two.
>> --
>> David Gugick
>> Quest Software
>> www.imceda.com
>> www.quest.com
>|||/PAE is only required for > 4 GB. AWE can be enabled before then. And,
/3GB should be enabled all the time up to 16 GB, but on Win2K3, you should
use the USERVA to start scalling back from 3 GB around 12 GB of ram or so.
Again, if you are only using Standard Edition Win2K, /3GB is NOT supported.
Sincerely,
Anthony Thomas
"Wojtek Garwol" <garwol@.usunto.poczta.fm> wrote in message
news:d7qj6e$jsu$1@.nemesis.news.tpi.pl...
"Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
news:uaW1M4HaFHA.2212@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I have setup the /3Gb option in the boot.ini file because my server has
> 4Gb of RAM.
> But SQL Server still use only 1.7Gb.
> on another server, there is no problems, the same parameters and SQL
> Server use more then 2Gb of memory!!!
> there is anything missing ?
> what can I check?
Use /pae in boot.ini and enable awe in SQL Server, then your SQL should be
able to consume ca. 3.75 GB of RAM (W2K AS + SQL EE SP3)
Regards
Wojtek|||I think its the standard edition of SQL 2000.
I'll check this.
but...
on another environment the memory usage go up to 2.7gb.
its a Win 2003 Ent. server (SP1) + SQL 2000 enterprise (SP4)
4 Gb of memory, 2.7g used by SQL and 512mb of free memory.
there is no upper limit usage for SQL Server.
the /3Gb option is enabled AWE disabled.
why SQL don't use more memory?
any missing option in this case?
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:O8Sh0AQaFHA.3876@.TK2MSFTNGP12.phx.gbl...
> You still need SQL Enterprise Edition to use more than 2GB. It sounds
> like you are using Standard Edition of SQL Server. What does @.@.Version
> show?
> --
> Andrew J. Kelly SQL MVP
>
> "Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
> news:uJz3PVKaFHA.612@.TK2MSFTNGP12.phx.gbl...
>> Yes, SP4 installed
>> on a Win 2003 Enterprise edition server
>> AWE is NOT enable on the server.
>> For a 4Gb system what is the best option?
>> /3Gb
>> /3Gb + AWE
>> /PAE
>> /PAE + AWE
>> /3Gb /PAE
>> /3Gb /PAE + AWE
>> ?
>>
>> "David Gugick" <david.gugick-nospam@.quest.com> wrote in message
>> news:eYe9KLIaFHA.616@.TK2MSFTNGP12.phx.gbl...
>> Jéjé wrote:
>> Hi,
>> I have setup the /3Gb option in the boot.ini file because my server
>> has 4Gb of RAM.
>> But SQL Server still use only 1.7Gb.
>> on another server, there is no problems, the same parameters and SQL
>> Server use more then 2Gb of memory!!!
>> there is anything missing ?
>> what can I check?
>> thanks.
>> Jerome.
>> Are you running SQL 2000 Service Pack 4? If so, there's a known issue
>> with AWE that is going to be addressed with a hotfix in the next week or
>> two.
>> --
>> David Gugick
>> Quest Software
>> www.imceda.com
>> www.quest.com
>>
>|||This is a multi-part message in MIME format.
--030301010703050100030701
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
The reason SQL memory allocation is only going up to 2.7G is because a
Win32 process can only address 4G of RAM (without changes to the memory
model, like PAE & AWE). This 4G is split up into 2 components: user
addressable memory & kernel addressable memory. The split is normally
2G/2G but when you specify the /3GB switch in boot.ini this means the OS
will only allocate a maximum of 1G to the kernel for each process. So
this means that when addressing 4G of memory the kernel code will
address 1G and the user code will address 3G of memory (hence the /3GB
switch - it would be more accurate to call it the "/1GB" switch because
that's the bit it's really limiting).
To address more than 4GB of memory you have to either switch to 64-bit
or change the memory management strategy, for example by using PAE &
AWE. But in your case, with 4GB of physical RAM in the box and the /3GB
boot.ini switch enabled, the memory ceiling for SQL Server will be 3GB,
and 2.7GB is getting pretty close. Remember SQL Server will, by
default, release memory when other applications request memory and there
is none left (it tries to maintain a free memory threshold of 10MB by
default) because of the dynamic memory management model SQL has implemented.
HTH
--
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
Jéjé wrote:
>I think its the standard edition of SQL 2000.
>I'll check this.
>but...
>on another environment the memory usage go up to 2.7gb.
>its a Win 2003 Ent. server (SP1) + SQL 2000 enterprise (SP4)
>4 Gb of memory, 2.7g used by SQL and 512mb of free memory.
>there is no upper limit usage for SQL Server.
>the /3Gb option is enabled AWE disabled.
>why SQL don't use more memory?
>any missing option in this case?
>"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
>news:O8Sh0AQaFHA.3876@.TK2MSFTNGP12.phx.gbl...
>
>>You still need SQL Enterprise Edition to use more than 2GB. It sounds
>>like you are using Standard Edition of SQL Server. What does @.@.Version
>>show?
>>--
>>Andrew J. Kelly SQL MVP
>>
>>"Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
>>news:uJz3PVKaFHA.612@.TK2MSFTNGP12.phx.gbl...
>>
>>Yes, SP4 installed
>>on a Win 2003 Enterprise edition server
>>AWE is NOT enable on the server.
>>For a 4Gb system what is the best option?
>>/3Gb
>>/3Gb + AWE
>>/PAE
>>/PAE + AWE
>>/3Gb /PAE
>>/3Gb /PAE + AWE
>>?
>>
>>"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
>>news:eYe9KLIaFHA.616@.TK2MSFTNGP12.phx.gbl...
>>
>>Jéjé wrote:
>>
>>Hi,
>>I have setup the /3Gb option in the boot.ini file because my server
>>has 4Gb of RAM.
>>But SQL Server still use only 1.7Gb.
>>on another server, there is no problems, the same parameters and SQL
>>Server use more then 2Gb of memory!!!
>>there is anything missing ?
>>what can I check?
>>thanks.
>>Jerome.
>>
>>Are you running SQL 2000 Service Pack 4? If so, there's a known issue
>>with AWE that is going to be addressed with a hotfix in the next week or
>>two.
>>--
>>David Gugick
>>Quest Software
>>www.imceda.com
>>www.quest.com
>>
>>
>>
>
>
--030301010703050100030701
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>The reason SQL memory allocation is only going up to 2.7G is
because a Win32 process can only address 4G of RAM (without changes to
the memory model, like PAE & AWE). This 4G is split up into 2
components: user addressable memory & kernel addressable memory.
The split is normally 2G/2G but when you specify the /3GB switch in
boot.ini this means the OS will only allocate a maximum of 1G to the
kernel for each process. So this means that when addressing 4G of
memory the kernel code will address 1G and the user code will address
3G of memory (hence the /3GB switch - it would be more accurate to call
it the "/1GB" switch because that's the bit it's really limiting). 
 
To address more than 4GB of memory you have to either switch to 64-bit
or change the memory management strategy, for example by using PAE
& AWE. But in your case, with 4GB of physical RAM in the box and
the /3GB boot.ini switch enabled, the memory ceiling for SQL Server
will be 3GB, and 2.7GB is getting pretty close. Remember SQL Server
will, by default, release memory when other applications request memory
and there is none left (it tries to maintain a free memory threshold of
10MB by default) because of the dynamic memory management model SQL has
implemented. 
 
HTH 
</tt>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
-- 
 mike
hodgson | database administrator
| mallesons stephen jaques 
T +61 (2) 9296 3668 | F +61
(2) 9296 3885 | M +61
(408) 675 907 
E
<a href="http://links.10026.com/?link=mailto:mike.hodgson@.mallesons.nospam.com">
mailto:mike.hodgson@.mallesons.nospam.com</a> | W <a href="http://links.10026.com/?link=/">http://www.mallesons.com">
http://www.mallesons.com</a> 
</div>
 
 
Jéjé wrote:
<blockquote cite="miduIfJy7IcFHA.2688@.TK2MSFTNGP14.phx.gbl" type="cite">
<pre wrap="">I think its the standard edition of SQL 2000.
I'll check this.
but...
on another environment the memory usage go up to 2.7gb.
its a Win 2003 Ent. server (SP1) + SQL 2000 enterprise (SP4)
4 Gb of memory, 2.7g used by SQL and 512mb of free memory.
there is no upper limit usage for SQL Server.
the /3Gb option is enabled AWE disabled.
why SQL don't use more memory?
any missing option in this case?
"Andrew J. Kelly" <a class="moz-txt-link-rfc2396E" href="http://links.10026.com/?link=mailto:sqlmvpnooospam@.shadhawk.com"><sqlmvpnooospam@.shadhawk.com></a> wrote in message
<a class="moz-txt-link-freetext" href="http://links.10026.com/?link=news:O8Sh0AQaFHA.3876@.TK2MSFTNGP12.phx.gbl">news:O8Sh0AQaFHA.3876@.TK2MSFTNGP12.phx.gbl</a>...
</pre>
<blockquote type="cite">
<pre wrap="">You still need SQL Enterprise Edition to use more than 2GB. It sounds
like you are using Standard Edition of SQL Server. What does @.@.Version
show?
--
Andrew J. Kelly SQL MVP
"Jéjé" <a class="moz-txt-link-rfc2396E" href="http://links.10026.com/?link=mailto:willgart_A_@.hotmail_A_.com"><willgart_A_@.hotmail_A_.com></a> wrote in message
<a class="moz-txt-link-freetext" href="http://links.10026.com/?link=news:uJz3PVKaFHA.612@.TK2MSFTNGP12.phx.gbl">news:uJz3PVKaFHA.612@.TK2MSFTNGP12.phx.gbl</a>...
</pre>
<blockquote type="cite">
<pre wrap="">Yes, SP4 installed
on a Win 2003 Enterprise edition server
AWE is NOT enable on the server.
For a 4Gb system what is the best option?
/3Gb
/3Gb + AWE
/PAE
/PAE + AWE
/3Gb /PAE
/3Gb /PAE + AWE
?
"David Gugick" <a class="moz-txt-link-rfc2396E" href="http://links.10026.com/?link=mailto:david.gugick-nospam@.quest.com"><david.gugick-nospam@.quest.com></a> wrote in message
<a class="moz-txt-link-freetext" href="http://links.10026.com/?link=news:eYe9KLIaFHA.616@.TK2MSFTNGP12.phx.gbl">news:eYe9KLIaFHA.616@.TK2MSFTNGP12.phx.gbl</a>...
</pre>
<blockquote type="cite">
<pre wrap="">Jéjé wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi,
I have setup the /3Gb option in the boot.ini file because my server
has 4Gb of RAM.
But SQL Server still use only 1.7Gb.
on another server, there is no problems, the same parameters and SQL
Server use more then 2Gb of memory!!!
there is anything missing ?
what can I check?
thanks.
Jerome.
</pre>
</blockquote>
<pre wrap="">Are you running SQL 2000 Service Pack 4? If so, there's a known issue
with AWE that is going to be addressed with a hotfix in the next week or
two.
--
David Gugick
Quest Software
<a class="moz-txt-link-abbreviated" href="http://links.10026.com/?link=www.imceda.com</a>">http://www.imceda.com">www.imceda.com</a>
<a class="moz-txt-link-abbreviated" href="http://links.10026.com/?link=www.quest.com</a>">http://www.quest.com">www.quest.com</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<pre wrap=""><!-->
</pre>
</blockquote>
</body>
</html>
--030301010703050100030701--|||The other .3GB is used by MemToLeave and does not show in Task manager like
the memory pool does. That is perfectly normal for 4GB of ram with /3GB set
and Enterprise Edition.
--
Andrew J. Kelly SQL MVP
"Jéjé" <willgart@.BBBhotmailAAA.com> wrote in message
news:uIfJy7IcFHA.2688@.TK2MSFTNGP14.phx.gbl...
>I think its the standard edition of SQL 2000.
> I'll check this.
> but...
> on another environment the memory usage go up to 2.7gb.
> its a Win 2003 Ent. server (SP1) + SQL 2000 enterprise (SP4)
> 4 Gb of memory, 2.7g used by SQL and 512mb of free memory.
> there is no upper limit usage for SQL Server.
> the /3Gb option is enabled AWE disabled.
> why SQL don't use more memory?
> any missing option in this case?
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:O8Sh0AQaFHA.3876@.TK2MSFTNGP12.phx.gbl...
>> You still need SQL Enterprise Edition to use more than 2GB. It sounds
>> like you are using Standard Edition of SQL Server. What does @.@.Version
>> show?
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
>> news:uJz3PVKaFHA.612@.TK2MSFTNGP12.phx.gbl...
>> Yes, SP4 installed
>> on a Win 2003 Enterprise edition server
>> AWE is NOT enable on the server.
>> For a 4Gb system what is the best option?
>> /3Gb
>> /3Gb + AWE
>> /PAE
>> /PAE + AWE
>> /3Gb /PAE
>> /3Gb /PAE + AWE
>> ?
>>
>> "David Gugick" <david.gugick-nospam@.quest.com> wrote in message
>> news:eYe9KLIaFHA.616@.TK2MSFTNGP12.phx.gbl...
>> Jéjé wrote:
>> Hi,
>> I have setup the /3Gb option in the boot.ini file because my server
>> has 4Gb of RAM.
>> But SQL Server still use only 1.7Gb.
>> on another server, there is no problems, the same parameters and SQL
>> Server use more then 2Gb of memory!!!
>> there is anything missing ?
>> what can I check?
>> thanks.
>> Jerome.
>> Are you running SQL 2000 Service Pack 4? If so, there's a known issue
>> with AWE that is going to be addressed with a hotfix in the next week
>> or two.
>> --
>> David Gugick
>> Quest Software
>> www.imceda.com
>> www.quest.com
>>
>>
>

Thursday, March 8, 2012

.Net Deployment ....

Hi everybody,

I want install the project in client side .. In installation time i want to access the my server .. How i can make the setup file to access the internet.. please help me.....

Thanks & Regards,

S.Sajan

Not only is that NOT a good idea, many users will have firewalls that may keep your installation from accessing the internet.

See my post to your previous question for information about remote and unattended installations.

Thursday, February 16, 2012

*.sql

I want to setup a weblog and I us .Text for it. It includes several .sql files and they are there for making my database (I think). How can I execute them so they make my database?? Thanks, Roelif the db is sql server, you can run the sql scripts from the *.sql file in QA...

HTH|||To elaborate further, if you have Query Analyzer, you can do a File...Open...and open the .SQL file. This will open up the script in a readable format. Then you do Query...Execute to run it.

If you do not have Query Analyzer, you can use the command-line OSQL utility.

osql -S (local) -E -i c:\SQLScript.sql

Terri|||If I do so then there are no tables created but there are stored procedures made. Is this okay??

Roel|||Well, the stored procedure won't be able to run without the tables being there, so no, in that sense it is not OK. But both QA and OSQL will let you create the stored procedures without the tables.

How are you planning on creating the tables? Didn't they supply scripts for that, too?

Terri|||I don't know. I think you must create tables wich match witch the stored procedures. But I will go with my question to the .Text department of this forum. Thanx

Thursday, March 22, 2012

Turning Off TCP/IP Client Has No Effect ?

Tuesday, March 20, 2012

/L*v C:\temp\logfile

/3Gb option set, but SQL Server use only 1.7Gb....

/3Gb option set, but SQL Server use only 1.7Gb....

/3Gb option set, but SQL Server use only 1.7Gb....

Thursday, March 8, 2012

.Net Deployment ....

Thursday, February 16, 2012

*.sql

SQL SQLExpress

Blog Archive

About Me