October 5, 2005 at 10:15 am
We're moving MSDE 2000 to SQL 2000 ED. I'm little concerned since we don’t have any QA or DEV env for this box…I don’t really have much choice as far as testing goes. Has anybody faced any issues in similar situation? Any feed back would be greatly appreciated. Thanks
October 6, 2005 at 4:36 am
Hi There.
Personally I've never had any problems with it.
We've been using MSDE as a tablet PC database and synchronizing it with SQL 2000 as the central server. I've seen no issues going back and forth. In fact, often times I'll do personal development with MSDE, script the tables and sps, and move to SQL Server. In terms of T-SQL, DDL, indices, and stored procs, they seem to work exactly the same.
From what I know, MSDE is essentially the same code as SQL 2000, just limited in its licensing and parallel processing capabilities (number of CPUs, memory, etc.).
You should be fine. Use the Red-Gate Database compare $200ish or DABCOS (free - from SourceForge) for DDL/sp/UDF compares.
October 6, 2005 at 6:00 am
You won't have an issue. If you want to compare what the editions have to offer, look up this URL from Microsoft:
http://download.microsoft.com/download/8/1/7/817bb6e6-9d97-4a5d-be8d-508256ae4045/ChoosEd.doc
MSDE (Desktop Engine in 2000 release) has a hard-coded concurrency governor limit that limits the workload to 8 concurrenct connections. It does not stop providing more connections after this limit is exceeded but makes it sluggish (look-up DBCC CONCURRENCYVIOLATION command in BOL to see more about this). There is also a 2GB size limitation. SQL Server 2005 Express on the other hand has removed some of these limitations like the concurrency governor check - but has other resource limitations like it can use only one processor, limited memory.
Hth
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply