Re: MOSS2007 and SQL2005 on Single Server

My understanding is that it is *any* database. However naturally that is likely to be a content database ...

I doubt if they seriously expect anyone to run production MOSS using this thing. They would probably actually prefer that no-one runs MOSS in production on anything less than 2 servers so it's imo intentionally crippled.

The version for WSS 3.0 isn't because a single server setup is quite feasible for that (and it provides a low price entry point is no doubt another reason).

Mike Walsh

WSS FAQ http://www.wssfaq.com

no questions by e-mail please



AJ wrote:
On 18 Jun, 12:55, "Mike Walsh" <englantilai...@xxxxxxxxxxx> wrote:
The only issue is in a year's time, the
database size will require you to upgrade to SQL Server
With MOSS 2007 this would be true (there is a limit of 4GB in the database
size, which I presume is what you are refering to).

However with WSS 3.0 (which you seem to be suggesting he should use) there
isn't such a problem as the free version of embedded SQL Server 2005 Express
("Windows Internal Database" is the new official name) that you get with WSS
3.0 doesn't have any database size restriction.

I didn't want to go into that in my reply which is why I just left it (for
*Moss*) as "I hope you are using real SQL Server" ... (to avoid that 4GB
limit).

Mike Walsh

"SmartbizAustralia" <t...@xxxxxxxxxxxxxxx> wrote in message

news:1182167053.136355.160160@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



If you are hosting this yourself start with Windows 2003 and install
WSS3.
You can later move up to Moss, but for the number of users the costs
are quite high.
Even the versions of SQL is not an issue initially. You can run all of
this with SQL Express. The only issue is in a year's time, the
database size will require you to upgrade to SQL Server and by then
SQL Server 2008 might be out.
i.e. Your system will need to grow as the load on it increases.
Regards,
Tom Bizannes
Sydney, Australia- Hide quoted text -
- Show quoted text -

Thanks to the both of you.

I was planning on using the full blown SQL product and not using the
flavour with the 4GB limit.
Is this a restriction of the content database i.e. where documents etc
will be stored. Seems very small. Wouldn't take anyone 5 minutes to
fill this up, or am I mis understanding?
WSS3.0 is out of the question as the customer already has MOSS2007
installed and they want to continue to use this, even though WSS would
be more suited.
Thanks
AJ

.

Relevant Pages

  • RE: WSS install locked into MSDE DB - Can not install for SQL Serv
    ... We have been using the WSS Web Admin interface. ... directing WSS to use SQL server. ... > Extend And Create A Content Database. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: SharePoint Services 3.0 unable to display content
    ... When connecting to the original configuration database, ... You are correct about the SQL Server. ... I am 100% about the WSS. ... Microsoft Windows SharePoint Services 2.0 ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: MOSS2007 and SQL2005 on Single Server
    ... I concur with Mike's response referencing deployment of a low cost ... The version for WSS 3.0 isn't because a single server setup is quite ... database size will require you to upgrade to SQL Server ...
    (microsoft.public.sharepoint.portalserver)
  • Re: MS Access DAO -> ADO.NET Migration
    ... William Vaughn ... Microsoft MVP ... Hitchhiker's Guide to Visual Studio and SQL Server ... My migration app works building a SSCE database file with imported data ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: MSDE users guide
    ... You are "right on" with your understanding of my problem. ... I am going to download the ... MSDE is missing a key component of SQL Server, ... basic tool for database creation and probing existing databases. ...
    (microsoft.public.dotnet.languages.csharp)