Showing posts with label appear. Show all posts
Showing posts with label appear. Show all posts

Sunday, March 11, 2012

AWE, SQL Server Enterprise, W2k STANDARD + 4GB RAM

Hi
Enabling AWE on SQL Enterprise Ed on a W2K STANDARD ed does appear to work (there seemed to be some doubt). I have reserved 3.5GB max server memory, and it has been allocated. The AWE counters in perfmon also seem to indicate it is functioning.
Does anyone have any experience with this configuration (good or bad)?
Also, any tips as to monitor memory usage - SQLServer/SQL Cache Memory doesn't appear to be of any use.
RegardsHi Stuart,
Not sure what you have done yet, but refers to the following article for
configuring AWE on SQL Server
HOW TO: Configure memory for more than 2 GB in SQL Server
http://support.microsoft.com/defaul...kb;en-us;274750
On 24 Mar 2004 08:04:17 -0800, Stuart wrote:

> Hi
> Enabling AWE on SQL Enterprise Ed on a W2K STANDARD ed does appear to
> work (there seemed to be some doubt). I have reserved 3.5GB max server
> memory, and it has been allocated. The AWE counters in perfmon also
> seem to indicate it is functioning.
> Does anyone have any experience with this configuration (good or bad)?
> Also, any tips as to monitor memory usage - SQLServer/SQL Cache Memory
> doesn't appear to be of any use.
> Regards
> Stuart|||Thanks - have read the MS articles (they often seem contradictory as
to whether AWE would work on W2k Server Standard)
However, even though AWE it does work on W2K server, there seems to be
some doubt as to whether there is any point in doing this, e.g.
http://www.sql-server-performance.com/awe_memory.asp says should leave
AWE off for my config.
To date, the config is looking quite good - enabling AWE has doubled
the available RAM to SQL and the Page Life Expectancy has gone up to
about 3 hours (up from a few seconds) .
Regards
Stuart
Yih-Yoon Lee <yihyoon@.hotmail.com> wrote in message news:<1lywgm6zbxldi.sdsrs0dj91ss$.dlg@.4
0tude.net>...
> Hi Stuart,
> Not sure what you have done yet, but refers to the following article for
> configuring AWE on SQL Server
> HOW TO: Configure memory for more than 2 GB in SQL Server
> http://support.microsoft.com/defaul...kb;en-us;274750
> On 24 Mar 2004 08:04:17 -0800, Stuart wrote:
>

Sunday, February 12, 2012

Auto-refresh the output of the 'Open Table" action

I checked the options in SQL 2005 Management Studio and it does not appear to be an
available functionality.
Is it possible to have the output of the "Open table" action to refresh the output at a
specified interval?
Thanks.
Probably not as it was never designed for that. There are few reasons to
use that functionality in the first place. The query editior is far more
flexible and does not run the risk of editing data by mistake just from
viewing the data.
Andrew J. Kelly SQL MVP
"Gaetan" <me@.somewhere.com> wrote in message
news:ge2h125kt8381rls43qv4ie3181j1c981r@.4ax.com...
>I checked the options in SQL 2005 Management Studio and it does not appear
>to be an
> available functionality.
> Is it possible to have the output of the "Open table" action to refresh
> the output at a
> specified interval?
> Thanks.
|||I understand the limitations of "Open table". The Query Editor is far more flexible but
unless I missed something, it too does not allow the SQL statements to be auto-rerun at
configurable interval.
On Wed, 15 Mar 2006 19:52:00 -0500, "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote:

>Probably not as it was never designed for that. There are few reasons to
>use that functionality in the first place. The query editior is far more
>flexible and does not run the risk of editing data by mistake just from
>viewing the data.
|||Not as a built in feature but a simple while loop will do it for you. This
will rerun the query every to seconds for 10 loops. Or what ever you need
it to do.
DECLARE @.X INT
SET @.X = 0
WHILE @.x < 10
BEGIN
SELECT *****
WAITFOR DELAY '00:00:10'
END
Andrew J. Kelly SQL MVP
"Gaetan" <me@.somewhere.com> wrote in message
news:6kej12dd7b63n4cq7tr61j26iejd9g7pv9@.4ax.com... [vbcol=seagreen]
>I understand the limitations of "Open table". The Query Editor is far more
>flexible but
> unless I missed something, it too does not allow the SQL statements to be
> auto-rerun at
> configurable interval.
>
> On Wed, 15 Mar 2006 19:52:00 -0500, "Andrew J. Kelly"
> <sqlmvpnooospam@.shadhawk.com> wrote: