//  home   //  advanced search   //  news   //  categories   //  sql build chart   //  downloads   //  statistics
 ASP FAQ 
Home
ASP FAQ Tutorials

   8000XXXX Errors
   Alerts
   ASP.NET 2.0
   Classic ASP 1.0
   Databases
      Access DB & ADO
      General SQL Server & Access Articles
      MySQL
      Other Articles
      Schema Tutorials
      Sql Server 2000
      Sql Server 2005
   General Concepts
   Search Engine Optimization (SEO)

Contact Us
Site Map

Search

Web
aspfaq.com
tutorials.aspfaq.com
databases.aspfaq.com

ASP FAQ Tutorials :: Databases :: Other Articles :: What are the limitations of MSDE?


What are the limitations of MSDE?

All SQL Server 2000 versions (as well as several other Microsoft products; see KB #324998) ship with SQL Server 2000 Desktop Edition, often referred to as MSDE (Microsoft Data Engine) 2.0. Essentially, MSDE is a version of SQL Server that you can distribute with applications. As such, it is slightly lighter weight, and has some notable restrictions. Other than the following list, however, MSDE and the other editions of SQL Server have very similar behavior and performance characteristics (see Article #2345 for a technical comparison). 
  • an MSDE database can be no larger than 2 GB (this includes MDF and NDF files only — log sizes are not included in the size limit); 
     
  • performance throttling occurs when there are more than five (5) concurrent workload batches in progress (this does *not* mean 5 concurrent *users* — with a properly build application, you can certainly support more. For more detailed information about the query governor, see this MSDN topic); 
     
  • MSDE cannot be a publisher in transaction replication, and when acting as publisher in all other types of replication, must also be the distributor; 
     
  • MSDE does not ship with GUI administrative tools such as Enterprise Manager or Query Analyzer -- see Article #2442 for alternative administration tools; 
     
  • MSDE does not support SQL Mail (see Article #2403 for alternatives); 
     
  • MSDE does not offer OLAP / data warehousing capabilities; and, 
     
  • MSDE does not come with Books Online, but you can download it from Microsoft downloads (updated January, 2004).
The licensing issues surrounding MSDE have long needed to be clarified—perhaps Microsoft SQL Server: SQL Server 2005 Ex... is a good start. 
 
There are also some other minor differences in MSDE that you should be aware of... this article goes into detail about them, and this product matrix might be useful as well. 
 
You can also look at this WebCast in KB #817788, which details issues surrounding installing, deploying, and maintaining MSDE. 
 
And for a verbose commentary on MSDE, see SoftwareEng's WiKi
 

SQL Server Express 2005 
 
As of July 2004, these are the planned limitations of the next generation of MSDE, now known as SQL Server Express (which will still be a free product): 
  • 1 GB memory (for buffer, not total); 
     
  • 1 CPU; 
     
  • 50 named instances per machine; 
     
  • 4 GB per database (not including log files); 
     
  • transactional replication is limited to a subscriber role only; 
     
  • data mirroring and clustering are not available; 
     
  • full-text search is not available; 
     
  • SQL Agent is not available (you can use Service Broker or Task Scheduler instead); 
     
  • the DTS Runtime is not available (though you can use DTS in Express from other machines); 
     
  • Reporting Services is not available; and, 
     
  • Business Intelligence is not available (this includes Notification Services and Analysis Services).
There is no more workload governor, though if you are running Express on Windows XP Home or Windows 2000/XP Professional, and using named pipes to connect, you are limited to 5 and 10 simultaneous connections, respectively. This is enforced at the OS level, and is not a new limitation in SQL Server Express; it also exists in previous versions of MSDE and SQL Server Personal Edition. 
 
There will be a limited graphical management tool for SQL Express, however it will not ship until as late as mid-2006. In the meantime, you can access SQL Server Express through SQLCMD, the new command-line admin interface to SQL Server; with Management Studio from any other SQL Server edition; or, from a subset of the applications listed in Article #2442.

Related Articles

How do I build a query with optional parameters?
How do I calculate the median in a table?
How do I create a store locator feature?
How do I deal with MEMO, TEXT, HYPERLINK, and CURRENCY columns?
How do I deal with multiple resultsets from a stored procedure?
How do I debug my SQL statements?
How do I determine if a column exists in a given table?
How do I enable or disable connection pooling?
How do I enumerate through the DSNs on a machine?
How do I find a stored procedure containing <text>?
How do I get a list of Access tables and their row counts?
How do I get the latest version of the JET OLEDB drivers?
How do I handle alphabetic paging?
How do I handle BIT / BOOLEAN columns?
How do I handle error checking in a stored procedure?
How do I ignore common words in a search?
How do I page through a recordset?
How do I present one-to-many relationships in my ASP page?
How do I prevent duplicates in a table?
How do I prevent my ASP pages from waiting for backend activity?
How do I prevent NULLs in my database from mucking up my HTML?
How do I protect my Access database (MDB file)?
How do I protect my stored procedure code?
How do I protect myself against the W32.Slammer worm?
How do I remove duplicates from a table?
How do I rename a column?
How do I retrieve a random record?
How do I return row numbers with my query?
How do I send a database query to a text file?
How do I simulate an array inside a stored procedure?
How do I solve 'Could not find installable ISAM' errors?
How do I solve 'Operation must use an updateable query' errors?
How do I temporarily disable a trigger?
How do I use a SELECT list alias in the WHERE or GROUP BY clause?
How do I use a variable in an ORDER BY clause?
Should I index my database table(s), and if so, how?
Should I store images in the database or the filesystem?
Should I use a #temp table or a @table variable?
Should I use a view, a stored procedure, or a user-defined function?
Should I use recordset iteration, or GetRows(), or GetString()?
What are all these dt_ stored procedures, and can I remove them?
What are the limitations of MS Access?
What are the valid styles for converting datetime to string?
What datatype should I use for my character-based database columns?
What datatype should I use for numeric columns?
What does "ambiguous column name" mean?
What is this 'Multiple-step OLE DB' error?
What is wrong with 'SELECT *'?
What naming convention should I use in my database?
What should I choose for my primary key?
What should my connection string look like?
When should I use CreateObject to create my recordset objects?
Where can I get this 'Books Online' documentation?
Where do I get MSDE?
Which database platform should I use for my ASP application?
Which tool should I use: Enterprise Manager or Query Analyzer?
Why are there gaps in my IDENTITY / AUTOINCREMENT column?
Why can I not 'open a database created with a previous version...'?
Why can't I access a database or text file on another server?
Why can't I use the TOP keyword?
Why do I get 'Argument data type text is invalid for argument [...]'?
Why do I get 'Not enough space on temporary disk' errors?
Why does ASP give me ActiveX errors when connecting to a database?
Should I use COALESCE() or ISNULL()?
Where can I get basic info about using stored procedures?

 

 


Created: 8/9/2002 | Last Updated: 9/15/2005 | broken links | helpful | not helpful | statistics
© Copyright 2006, UBR, Inc. All Rights Reserved. (141)

 

Copyright 1999-2006, All rights reserved.
Finding content
Finding content.  An error has occured...