Showing posts with label mssql. Show all posts
Showing posts with label mssql. Show all posts

Tuesday, March 20, 2012

/3GB Switch

Hi All

Server 2003 standard edition, MSsql 2005 standard edition

As I understand it server 2003 standard only supports 4gb. Does this mean I can only use up to 4gb as the maximum memory for server 2005?

If that is the case I would like to use the 3GB switch, and leave the other gig for other apps. If I set the 3GB switch in boot.ini do I then also have to enable AWE (which I can't seem to do) or can I forget about AWE altogether?

Many thanks

Martin

Dear Martin.

If your server has 4GB or less of RAM, the "awe enabled" option should always be left to the default value of 0, which means that AWE memory is not being used. The /3GB switch is used to tell SQL Server to take advantage of 3GB out of the base 4GB of RAM that Windows supports natively. If you don't specify this option, then SQL Server will only take advantage of 2GB of the first 4GB of RAM in the server, essentially wasting 1GB of RAM.

If you'll set only /3GB switch and AWE will leave 0 it will be great.

Kind Regards,

Martin Bacik

|||

Hi Martin,

That answers my question perfectly. Many thanks

Martin (2)

|||

Hi again,

I set the 3gb switch and rebooted but I can't increase the maximum mermory spinform in server manager. I can't go above 2gb.

Any advice greatly appreciated

Best Regards

Martin

|||

Here's how to change in through the system stored proc:

Code Snippet

--To display all options

EXEC sp_configure 'show advanced options',1

RECONFIGURE

--To change the max server memory.

EXEC sp_configure 'max server memory (MB)', 3072

RECONFIGURE

--To switch off the display of all the options

EXEC sp_configure 'show advanced options',0

RECONFIGURE

Probably want to bounce the SQL service after that.

HTH

Ray

/3GB Switch

Hi All

Server 2003 standard edition, MSsql 2005 standard edition

As I understand it server 2003 standard only supports 4gb. Does this mean I can only use up to 4gb as the maximum memory for server 2005?

If that is the case I would like to use the 3GB switch, and leave the other gig for other apps. If I set the 3GB switch in boot.ini do I then also have to enable AWE (which I can't seem to do) or can I forget about AWE altogether?

Many thanks

Martin

Dear Martin.

If your server has 4GB or less of RAM, the "awe enabled" option should always be left to the default value of 0, which means that AWE memory is not being used. The /3GB switch is used to tell SQL Server to take advantage of 3GB out of the base 4GB of RAM that Windows supports natively. If you don't specify this option, then SQL Server will only take advantage of 2GB of the first 4GB of RAM in the server, essentially wasting 1GB of RAM.

If you'll set only /3GB switch and AWE will leave 0 it will be great.

Kind Regards,

Martin Bacik

|||

Hi Martin,

That answers my question perfectly. Many thanks

Martin (2)

|||

Hi again,

I set the 3gb switch and rebooted but I can't increase the maximum mermory spinform in server manager. I can't go above 2gb.

Any advice greatly appreciated

Best Regards

Martin

|||

Here's how to change in through the system stored proc:

Code Snippet

--To display all options

EXEC sp_configure 'show advanced options',1

RECONFIGURE

--To change the max server memory.

EXEC sp_configure 'max server memory (MB)', 3072

RECONFIGURE

--To switch off the display of all the options

EXEC sp_configure 'show advanced options',0

RECONFIGURE

Probably want to bounce the SQL service after that.

HTH

Ray

Monday, March 19, 2012

.sqlplan

is there a way to open a .sqlplan without have to install MSSQL Server?

There is no viewer for this. YOu will have to install SQL Server Management Studio to view the plans.

Jens K. Suessmeyer.

http://www.sqlserver2005.de

Thursday, March 8, 2012

.Net Framework Issue in the MSSQL 2000?

I have a problem regarding the framework that the MSSQL2000 have. Is the MSSQL2000 report services only support for the .NET framework 1.0? or it can support >NET framework 2.0? any help will be appreciated.Thanx God Bless

As mentioned in your other thread - Reporting Services 2000 only works with .NET/ASP.NET 1.1.

-- Robert

Sunday, February 19, 2012

..\MSSQL\Data\ - Directory saturated

C:\Program Files\Microsoft SQL Server\MSSQL\Data\" contains .mdb and
..ldb files that are huge, some reach 21GB! while backup files don't
exceed 8MB.

I guess it's a kind of transaction log, but I'm not sure.

Can I erase them all and lose no information?
Where I configure it to avoid it to happen in the future?

Thanks in advance.Try to shrink the database. Run the SQL Server Enterprise manager.
Right-click on the database of interest and select "all tasks | shrink
database" from the context menu. Try this witthout and then with the "move
pages" option checked. Free space "holes" can develop in your database as
storage expands and rows are added/deleted/updated. Doing index maintenance
may help, too but at 8MB vs 21GB, I'm thinking it's not just sparse page
fills but wholesale extents. You could set the databases for autoshrink but
this might cause operations in your database to slow down when you weren't
expecting it. Probably better to do it on a schedule.

You might also look at the properties and see how much space is used versus
allocated. Before looking at properties, be sure to right-click on the
database and do a "refresh" to get the figures updated.

Could be your log has never been dumped and truncated. You may have to set
up a maintenance plan. Check the Administrator's guide for advice. The log
is in the .LDF file.

"Pablo" <pablopettis@.yahoo.com> wrote in message
news:47ae7cc6.0407150630.4ad7be1d@.posting.google.c om...
> C:\Program Files\Microsoft SQL Server\MSSQL\Data\" contains .mdb and
> .ldb files that are huge, some reach 21GB! while backup files don't
> exceed 8MB.
> I guess it's a kind of transaction log, but I'm not sure.
> Can I erase them all and lose no information?
> Where I configure it to avoid it to happen in the future?
> Thanks in advance.|||Hi

Check out:
http://msdn.microsoft.com/library/d...ar_da2_1uzr.asp

If this is production machine you should think about moving the log files
onto a different set of spindles (disks/controller card) to the data files,
operating system and page file.

John

"Pablo" <pablopettis@.yahoo.com> wrote in message
news:47ae7cc6.0407150630.4ad7be1d@.posting.google.c om...
> C:\Program Files\Microsoft SQL Server\MSSQL\Data\" contains .mdb and
> .ldb files that are huge, some reach 21GB! while backup files don't
> exceed 8MB.
> I guess it's a kind of transaction log, but I'm not sure.
> Can I erase them all and lose no information?
> Where I configure it to avoid it to happen in the future?
> Thanks in advance.