Re: What version of SQL is on SBS R2 Standard and can I use it?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi,

Thanks for posting in our newsgroup.

The SQL server occupies large amount of RAM, which is by design. We can
modify the max server memory to prevent SQL Server from using more that the
specified amount of memory. Then test if the problem can be resoved:

To do so, open a command prompt and run the following command:

osql -E -S <SBS server name>\<instance name>

You will enter the osql command prompt. Run the commends below (replace
<xxx> with the maximum and minimum amount of memory respectively):
1> EXEC sp_configure 'show advanced options', 1
2> reconfigure
3> go
1> EXEC sp_configure 'min server memory', <xxx>
2> reconfigure
3> go
1> EXEC sp_configure 'max server memory', <xxx>
2> reconfigure
3> go

After doing the above steps, you may run the commands to check the
configured memory usage:

1> EXEC sp_configure
2> go

For more information, please see the article below:
321363 INF: SQL Server Memory Usage
http://support.microsoft.com/?id=321363

Hope this helps.

If you need further assistance, please don't hesitate to let me know.

Best regards,

Robert Li(MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================

This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.

=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
<Thread-Topic: What version of SQL is on SBS R2 Standard and can I use it?
<thread-index: Acg1TE0LSTbWHZ4oQaqShxTHjx5JYw==
<X-WBNR-Posting-Host: 207.46.19.168
<From: =?Utf-8?B?RGF2ZWluZmxh?= <Daveinfla@xxxxxxxxxxxxxxxxxxxxxxxxx>
<References: <0A265704-CA1A-48C7-90ED-258D495BF888@xxxxxxxxxxxxx>
<xn0fe72zxr1gcrr02p@xxxxxxxxxxxxxxxxxxxx>
<8AC5C85C-CAED-4E19-989A-5758EFAA3B03@xxxxxxxxxxxxx>
<7C459752-CF28-4E8F-80EE-E0E18DDC6248@xxxxxxxxxxxxx>
<uzZfeeVMIHA.2140@xxxxxxxxxxxxxxxxxxxx>
<Subject: Re: What version of SQL is on SBS R2 Standard and can I use it?
<Date: Sun, 2 Dec 2007 17:32:00 -0800
<Lines: 203
<Message-ID: <AB5F67AA-4191-4249-855D-AE5FEDD8838D@xxxxxxxxxxxxx>
<MIME-Version: 1.0
<Content-Type: text/plain;
< charset="Utf-8"
<Content-Transfer-Encoding: 7bit
<X-Newsreader: Microsoft CDO for Windows 2000
<Content-Class: urn:content-classes:message
<Importance: normal
<Priority: normal
<X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
<Newsgroups: microsoft.public.windows.server.sbs
<Path: TK2MSFTNGHUB02.phx.gbl
<Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:79568
<NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
<X-Tomcat-NG: microsoft.public.windows.server.sbs
<
<
<I followed your instructions and successfully installed SQL Express,
however
<I have a couple questions now that it's up and running.
<
<During the application install the applicaton didn't reconize the default
<instance (SQLEXPRESS) which was created so he had me re-run the setup
<selecting the acutal radial labeled "Default Instance". This created one
<called MSSQLSERVER which the application not only found, but now found the
<SQLEXPRESS and two MSDE instances.
<
<The question is since I'm not using the SQLEXPRESS instance can I get rid
of
<it? If so, HOW? It's currently using 107,300K of memory.
<
<Next question..as soon as I configured monitoring it started complaining
<about something using to much memory. A check indicated the the
MSSQLSERVER
<instance is using 530,064K of memory! How do I adjust this and what should
it
<be adjusted to?
<
<Surprisingly the MSDE (Sharepoint and Monitoring) are using less then
<60,000K each.
<
<Thanks,
<
<Dave
<
<
<
<"bass_player [SBS-MVP]" wrote:
<
<> Just accept the Default instance called SQLEXPRESS (it actually is
called a
<> named instance but default for SQL Express). A user level account works
<> fine. This is something new for 2005 as you need to have an account
with
<> administrative privileges in prior versions. The "sa" account is used
for
<> super administrative purposed within SQL Server and is not the same as
the
<> user-level account you've mentioned. That one is a service account.
Mixed
<> mode authentication has something to do with connection settings when
<> connecting to SQL Server - whether you would like to use a Windows
account
<> or a SQL Server acount. Collation settings have something to do with
storing
<> data in your database and it even affects case-sensitivity of data.
Just
<> use the default collation setting (Latin1_General) for your case. User
<> instances can be used so you can name your SQL Server/MSDE installations
and
<> manage them independent of the other. If you are installing SQL Server
<> Express and you are using the same instance name as an existing one, it
will
<> prompt you for an upgrade. Otherwise, you can have MSDE and 2005 Express
<> instances on your SBS machine. For built-in SBS applications like
<> SBSMONITORING, upgrading to SQL Server 2005 is not supported
<>
<> Hope this helps.
<>
<> "Daveinfla" <Daveinfla@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
<> news:7C459752-CF28-4E8F-80EE-E0E18DDC6248@xxxxxxxxxxxxxxxx
<> >
<> > Found a doc that steps me thru a typical install but have a couple
<> > specific
<> > question, one was the authentication but my vendor already specified
using
<> > sql authentication and the document kind of leans towards that.
<> >
<> > Do I install SQL Express as a "Default instance"? I assume this is OK
<> > since
<> > I believe this calls it SQLExpress and shouldn't interfere with
anything.
<> >
<> > This doc suggests using a user level account, i.e. sqlexpressuser for
<> > security reasons. yes/no?
<> >
<> > The author also suggested Mixed mode (SQL authentication), which
requires
<> > the assignment of a password to the sa account (duh!). Already covered
<> > above.
<> >
<> > What about Collation Settings? SQL collations for compatibly with
previous
<> > versions or the default Latin1_General? Does the fact that I'm
upgrading
<> > from
<> > MSDE on one application and MS Access on another have any bearing on
this
<> > choice?
<> >
<> > Can I Enable User Instances?
<> >
<> > Last does this replace/upgrades the MSDE on SBS 2003 STD or is it a
<> > parallel
<> > install which will require moving the SBS instances manually. I
believe I
<> > read the later was the case but I can't find it now.
<> >
<> > Thanks,
<> >
<> > Dave
<> >
<> >
<> > "Daveinfla" wrote:
<> >
<> >>
<> >> Thanks for the answers guy...I did some further investigating, called
the
<> >> vendor, and it's recommend I go with SQL2005 Express as it allows for
up
<> >> to a
<> >> 4GB database vs. MSDE which only supports 2GB. There no where near
that,
<> >> but
<> >> nothing like planing ahead.
<> >>
<> >> Two questions:
<> >>
<> >> 1. Can someone point me to a white paper explaining step by step on
how
<> >> to
<> >> install SQL2005 Express on an existing SBS 2003 Standard server?
<> >>
<> >> 2. There are two versions listed for download, one with and one
without
<> >> advanced services, and a toolkit. From what I can tell, running as a
<> >> backend
<> >> server I should use the advanced services version, it this correct?
Do I
<> >> need
<> >> the tools?
<> >>
<> >> Thanks,
<> >>
<> >> Dave
<> >>
<> >>
<> >>
<> >> "Steve Foster [SBS MVP]" wrote:
<> >>
<> >> > Daveinfla wrote:
<> >> >
<> >> > >
<> >> > >OK I'm a bit light on the SQL training, OK a lot; I use the paint
by
<> >> > >number
<> >> > >method!
<> >> > >
<> >> > >I'm setting up a new server for a client which was ordered with
SBS
<> >> > >2003 R2
<> >> > >Standard, of course as luck would have it we discovered after the
fact
<> >> > >they
<> >> > >have two applications that use SQL databases. Actually one is
<> >> > >currently
<> >> > >configured to use MSDE 2000 and the other is using Access but will
<> >> > >support
<> >> > >SQL and we will be migrating that to SQL in the near future.
<> >> >
<> >> > If the application vendor supports MSDE, then you're fine with MSDE.
<> >> >
<> >> >
<> >> > >If I'm not mistaken SBS 2003 R2 ships with MSDE installed for
running
<> >> > >monitoring, SharePoint and one other instance. What version of
MSDE is
<> >> > >it
<> >> > >and
<> >> > >can it support 2 more instances? Keep in mind the two applications
<> >> > >will
<> >> > >only
<> >> > >have 2 users accessing them at any given time; it's a very small
<> >> > >office.
<> >> >
<> >> > You cannot legally use the MSDE that ships with SBS for hosting
<> >> > anything
<> >> > but the existing applications. That's a licencing restriction on
MSDE.
<> >> >
<> >> > However, you _can_ install another instance of MSDE if the
application
<> >> > vendor is shipping their product with MSDE, since that's licenced
<> >> > independently to the application vendor (MSDE licencing is a bit
weird,
<> >> > even by MS standards).
<> >> >
<> >> > >Take the following into consideration when making recommendations.
<> >> > >
<> >> > >I've been supplied instructions from the vendor on how to move the
<> >> > >application from the current server (desktop) running MSDE 2000 to
a
<> >> > >new
<> >> > >server with the following options:
<> >> > >
<> >> > >Option 1: Install on a full version of SQL Server 2005
<> >> > >Option 2: Move from MSDE to MSDE (old server to new server)
<> >> > >Option 3: Move from EXPRESS to EXPRESS
<> >> > >Option 4: Move from MSDE to EXPRESS
<> >> > >
<> >> > >From what I've read EXPESS ships on SBS 2003 R2 Premium, silly me I
<> >> > >thought
<> >> > >SBS Premium shipped with a full version of SQL, but $500 extra is
a
<> >> > >lot to
<> >> > >pay for Premium just to get SQL EXPRESS and since it's a very small
<> >> > >office
<> >> > >I'd like to avoid that option if possible.
<> >> >
<> >> > SBS2003 R2 Premium includes SQL2005 Workgroup. This is not the same
as
<> >> > SQL2005 Express. Express is the 2005 equivalent of MSDE.
<> >> >
<> >> > >What further confuses me is the fact that I've read EXPRESS is a
free
<> >> > >download. Can it be installed on SBS Standard and used at the
same
<> >> > >time
<> >> > >MSDE
<> >> > >is running? If so, doesn't that just leave ISA at a $500 price tag?
<> >> >
<> >> > SQL2005 Express is indeed a free download.
<> >> >
<> >> > It would be a possibility for the Access migration you're planning.
<> >> >
<> >> > Since your application vendor appears to support SQL2005 Express as
<> >> > well
<> >> > as MSDE, you can choose whichever suits you better for that (I'd
simply
<> >> > go
<> >> > with the vendors preferred choice).
<> >> >
<> >> > --
<> >> > Steve Foster [SBS MVP]
<> >> > ---------------------------------------
<> >> > MVPs do not work for Microsoft. Please reply only to the newsgroups.
<> >> >
<>
<>
<>
<

.

Relevant Pages

  • Re: FTS Performance in SQL 2005
    ... we had no end of problems with SQL FTS. ... Looking for a SQL Server replication book? ... The Memory Usage and VM Size never increase over about 65 MB and 20MB. ... cost relative to the whole batch, ...
    (microsoft.public.sqlserver.fulltext)
  • Re: FTS Performance in SQL 2005
    ... we had no end of problems with SQL FTS. ... Looking for a SQL Server replication book? ... The Memory Usage and VM Size never increase over about 65 MB and 20MB. ... cost relative to the whole batch, ...
    (microsoft.public.sqlserver.fulltext)
  • RE: Consolidating instances of SQL server
    ... SQL Server is designed to use memory. ... The maximum amount of memory SQL Server can use varies depending on your ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • RE: The DBMS returned an unspecified error.
    ... | We are using Microsoft's JDBC driver for Java database access to SQL ... | Insufficient memory available. ... even though SQL Server 2000 is configured to use up to the ... the problem is most likely in the MemToLeave ...
    (microsoft.public.sqlserver.jdbcdriver)
  • RE: server problems
    ... This newsgroup only focuses on SBS technical issues. ... >Thread-Topic: server problems ... >> web proxy service or SQL Server will normally use large memory. ...
    (microsoft.public.windows.server.sbs)