By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
458,124 Members | 1,566 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 458,124 IT Pros & Developers. It's quick & easy.

Simple way of telling if I'm using MSDE or full SQL Server?

P: n/a

I'm looking for a simple way of telling (inside a stored procedure) if I'm
currently using MSDE or a full SQL server. Ideally, there is some
pre-defined environment variable that won't cause me too much overhead. The
reason I'm doing this is because my system "rolls over" databases when it
reaches the 2Gb limit with MSDE, but obviously I want to avoid this overhead
if the user installs onto a full SQL server instance.

Thanks

Robin
Jul 23 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
Hi Robin,

Use the SQL statement:

select @@version

if it is MSDE it should have "...Desktop Engine..." in the returned
string, as opposed to eg "...Standard Edition..." on a "Standard"
install. (check to see what yours returns)

Hope this helps!

Paul.

Jul 23 '05 #2

P: n/a
Robin,

There is no 2GB database size limit in MSDE. That's just a rumor. It
simply has less features and a query governor.

Danny
<p_**********@hotmail.com> wrote in message
news:11**********************@f14g2000cwb.googlegr oups.com...
Hi Robin,

Use the SQL statement:

select @@version

if it is MSDE it should have "...Desktop Engine..." in the returned
string, as opposed to eg "...Standard Edition..." on a "Standard"
install. (check to see what yours returns)

Hope this helps!

Paul.

Jul 23 '05 #3

P: n/a
In article <Go*****************@newssvr17.news.prodigy.com> ,
is****@flash.net says...
Robin,

There is no 2GB database size limit in MSDE. That's just a rumor. It
simply has less features and a query governor.


Try again, directly from MS:
http://msdn.microsoft.com/library/de...l=/library/en-
us/replsql/replimpl_89cy.asp

The following limitations are MSDE 2000 limitations that can impact
replication:

* MSDE 2000 limits the size of the database to 2 gigabytes (GB). If MSDE
2000 is part of the replication topology, the size of the replicated
database is limited to 2 GB. If MSDE 2000 is the Subscriber, replication
agents fail after the database exceeds 2 GB. At that point, consider
upgrading the Subscriber to SQL Server Standard Edition.

* MSDE 2000 includes a workload governor, which starts slowing down the
database engine when more than eight operations are actively running at
the same time. The workload governor can affect replication performance.
In an active replication environment where there are a large number of
Subscribers, Microsoft recommends that you use either SQL Server
Standard Edition or Enterprise Edition as the Publisher or Distributor
instead of MSDE 2000.

http://msdn.microsoft.com/vstudio/do...examining.aspx

Q. How much data can MSDE 1.0 store?

A. MSDE 1.0 databases are limited to 2 gigabytes (GB) of data. This
limit is per database, and not per server, so a single MSDE server can
support multiple MSDE databases, each containing up to the 2 GB limit.
If you anticipate that your database is currently or will grow beyond 2
GB, consider upgrading to Microsoft SQL Server=3F 2000 Standard Edition
for a more scalable database platform on which to build.

--
--
sp*********@rrohio.com
(Remove 999 to reply to me)
Jul 23 '05 #4

P: n/a
Thanks for the tip :-p

"Leythos" <vo**@nowhere.org> wrote in message
news:MP************************@news-server.columbus.rr.com...
In article <Go*****************@newssvr17.news.prodigy.com> ,
is****@flash.net says...
Robin,

There is no 2GB database size limit in MSDE. That's just a rumor. It
simply has less features and a query governor.


Try again, directly from MS:
http://msdn.microsoft.com/library/de...l=/library/en-
us/replsql/replimpl_89cy.asp

The following limitations are MSDE 2000 limitations that can impact
replication:

* MSDE 2000 limits the size of the database to 2 gigabytes (GB). If MSDE
2000 is part of the replication topology, the size of the replicated
database is limited to 2 GB. If MSDE 2000 is the Subscriber, replication
agents fail after the database exceeds 2 GB. At that point, consider
upgrading the Subscriber to SQL Server Standard Edition.

* MSDE 2000 includes a workload governor, which starts slowing down the
database engine when more than eight operations are actively running at
the same time. The workload governor can affect replication performance.
In an active replication environment where there are a large number of
Subscribers, Microsoft recommends that you use either SQL Server
Standard Edition or Enterprise Edition as the Publisher or Distributor
instead of MSDE 2000.

http://msdn.microsoft.com/vstudio/do...examining.aspx

Q. How much data can MSDE 1.0 store?

A. MSDE 1.0 databases are limited to 2 gigabytes (GB) of data. This
limit is per database, and not per server, so a single MSDE server can
support multiple MSDE databases, each containing up to the 2 GB limit.
If you anticipate that your database is currently or will grow beyond 2
GB, consider upgrading to Microsoft SQL Server=3F 2000 Standard Edition
for a more scalable database platform on which to build.

--
--
sp*********@rrohio.com
(Remove 999 to reply to me)

Jul 23 '05 #5

P: n/a
Robin Tucker (id*************************@reallyidont.com) writes:
I'm looking for a simple way of telling (inside a stored procedure) if
I'm currently using MSDE or a full SQL server. Ideally, there is some
pre-defined environment variable that won't cause me too much overhead.
The reason I'm doing this is because my system "rolls over" databases
when it reaches the 2Gb limit with MSDE, but obviously I want to avoid
this overhead if the user installs onto a full SQL server instance.


This should cut it:

select serverproperty('Edition')
--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp
Jul 23 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.