MSDE 64-bit?

Hi there
Quick question.. can you get a 64-bit version of MSDE or do you need to
upgrade to SQL Server 2005 Express?
Thanks,
DanNo, there's no 64 bit MSDE. In fact, according to BOL, there's no 64 bit Express either (only WOW64
support).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"musosdev" <musoswire@.community.nospam> wrote in message
news:096D16D2-A5DF-4F5B-A380-6D67851F5512@.microsoft.com...
> Hi there
> Quick question.. can you get a 64-bit version of MSDE or do you need to
> upgrade to SQL Server 2005 Express?
> Thanks,
>
> Dan|||Thanks Tibor, but what's WOW64?! :o)
"Tibor Karaszi" wrote:
> No, there's no 64 bit MSDE. In fact, according to BOL, there's no 64 bit Express either (only WOW64
> support).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "musosdev" <musoswire@.community.nospam> wrote in message
> news:096D16D2-A5DF-4F5B-A380-6D67851F5512@.microsoft.com...
> > Hi there
> >
> > Quick question.. can you get a 64-bit version of MSDE or do you need to
> > upgrade to SQL Server 2005 Express?
> >
> > Thanks,
> >
> >
> > Dan
>|||Windows on Windows. It is the ability to run 32 bit Windows applications in a 64 bit Windows OS.
EM64T processors definitely has this, while I believe Itanium has very limited support for WOW64.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"musosdev" <musoswire@.community.nospam> wrote in message
news:8C59417B-D797-4E38-AAEA-F5BFA2126607@.microsoft.com...
> Thanks Tibor, but what's WOW64?! :o)
> "Tibor Karaszi" wrote:
>> No, there's no 64 bit MSDE. In fact, according to BOL, there's no 64 bit Express either (only
>> WOW64
>> support).
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "musosdev" <musoswire@.community.nospam> wrote in message
>> news:096D16D2-A5DF-4F5B-A380-6D67851F5512@.microsoft.com...
>> > Hi there
>> >
>> > Quick question.. can you get a 64-bit version of MSDE or do you need to
>> > upgrade to SQL Server 2005 Express?
>> >
>> > Thanks,
>> >
>> >
>> > Dan
>>|||Hi Dan,
Yes, there is no 64bit MSDE and SQL Express Edition.
For more information on WOW64, you may also refer to this article:
http://msdn.microsoft.com/library/shared/deeptree/asp/rightframe.asp?dtcfg=/
library/deeptreeconfig.xml&url=/library/en-us/win64/win64/running_32_bit_app
lications.asp?frame=true&hidetoc=false
Please feel free to let us know if you have any other questions or
concerns.
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||Hi musoswire,
Just check with you to see if you need further assistance on this issue.
Please feel free to post back if you have any other questions or concerns.
Have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================sql

MSDE 2000A Upgrade to SQL Express SP1 with Merge Replication

Hello,

I have the following scenario. An application using SQL Server 2000 SP3 on the server side and clients using MSDE 2000A (SP3a) on the client machine. Since the client is offline quite often merge replication is used to keep the clients in sync.

Now we try to upgrade to SQL Server 2005 SP1. The publisher and distributor upgrade (on the same box) worked fine and all clients could still synchronize. Fine :-)

Now we try to upgrade the clients to SQL Express SP1. Now the problems start :-(

1) After the upgrade the entry within the Synchronization Manager is gone (we can overcome this by using sp_MSregistersubscription or by manually disable and enable Synchronization manager on the subscription properties)

2) Initial Synchronization (takes a long time but) works fine, if I apply changes to the subscriber or force a reinitialize all following synchronization will fail. With the following messages:

Error messages:
The merge process could not clean up the subscription to 'tstvmw23':'TestBase:'TestBase'. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200965)
Get help: http://help/MSSQL_REPL-2147200965
New request is not allowed to start because it should come with valid transaction descriptor. (Source: MSSQLServer, Error number: 3989)
Get help: http://help/3989

Remark the test system I use is a nearly empty db (only with full schema and a few lookup tables) with 15MB. The same error occures if I create a new database an subscribe to the same publication.

Please help otherwise I'm forced to step back to MSDE.

Thanks in advance,

Thomas Hotz

Hi,

just to make sure you do not want SQL Server Express to the a merge replicant...

http://msdn2.microsoft.com/en-us/library/ms165616.aspx

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||What this table on the BOL means is that SQL Server Express cannot act as a Distributor/Publisher on a merge replication and the main cause is that it does not have an Agent.
http://technet.microsoft.com/en-us/library/ms143470.aspx
See the topic SQL Server does not include an agent on that reference.

SQL Server Express can act as a subscriber on Merge Replication though. If you have a type of subscription Pull, as the Agent runs on the subscribers you have to use RMO on your code to instantiate an agent or use Windows Synchronization Manager (Start Menu-> Accessories -> Synchronize)

We have SQLE running as subscribers on a pull merge replication topology...sql

MSDE 2000A Upgrade to SQL Express SP1 with Merge Replication

Hello,

I have the following scenario. An application using SQL Server 2000 SP3 on the server side and clients using MSDE 2000A (SP3a) on the client machine. Since the client is offline quite often merge replication is used to keep the clients in sync.

Now we try to upgrade to SQL Server 2005 SP1. The publisher and distributor upgrade (on the same box) worked fine and all clients could still synchronize. Fine :-)

Now we try to upgrade the clients to SQL Express SP1. Now the problems start :-(

1) After the upgrade the entry within the Synchronization Manager is gone (we can overcome this by using sp_MSregistersubscription or by manually disable and enable Synchronization manager on the subscription properties)

2) Initial Synchronization (takes a long time but) works fine, if I apply changes to the subscriber or force a reinitialize all following synchronization will fail. With the following messages:

Error messages:
The merge process could not clean up the subscription to 'tstvmw23':'TestBase:'TestBase'. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200965)
Get help: http://help/MSSQL_REPL-2147200965
New request is not allowed to start because it should come with valid transaction descriptor. (Source: MSSQLServer, Error number: 3989)
Get help: http://help/3989

Remark the test system I use is a nearly empty db (only with full schema and a few lookup tables) with 15MB. The same error occures if I create a new database an subscribe to the same publication.

Please help otherwise I'm forced to step back to MSDE.

Thanks in advance,

Thomas Hotz

Hi,

just to make sure you do not want SQL Server Express to the a merge replicant...

http://msdn2.microsoft.com/en-us/library/ms165616.aspx

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de
|||What this table on the BOL means is that SQL Server Express cannot act as a Distributor/Publisher on a merge replication and the main cause is that it does not have an Agent.
http://technet.microsoft.com/en-us/library/ms143470.aspx
See the topic SQL Server does not include an agent on that reference.

SQL Server Express can act as a subscriber on Merge Replication though. If you have a type of subscription Pull, as the Agent runs on the subscribers you have to use RMO on your code to instantiate an agent or use Windows Synchronization Manager (Start Menu-> Accessories -> Synchronize)

We have SQLE running as subscribers on a pull merge replication topology...

MSDE 2000 vs SQL express 2005 ??

Dear all,
We are starting a new developmement of our supervisiob system that will run
uner vista and we will use VS 2005 as a development platform ..
Based on that we need to select proper local database for our local data
archiving.
For that I will certainly us SQL express advance feature edition but some
say that there are connection limitation ?
As far as Icould read around, the only limitation there is is the 4GB
database sizte, 1 single processore handling, and 1GB of RAm for cachin
querries.
I did not get answer that sql express as a limitation in connection, is
there ?
Next I have heard also as an SQL personnal edition version.. Is it the MSDE
base on 2000 ? if its the case then it is not supported under Vista, si my
choice will be explain clearly then..
Thnaks for clarification and comments .
Regards
Serge
MCAD.NET
Thanks andrea, its clear now
"Andrea Montanari" wrote:

> hi Serge,
> calderara wrote:
> then you can only go for SQLExpress sp2 (not yet released)..
>
> tere aren't.. SQLExpress (as MSDE as well) does not include a component to
> limit connections.. it is limited as you already noticed..
> nope
>
> SQL Server Personal edition is based on SQL Server 2000 code base..
> regards
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
> -- remove DMO to reply
>
>
|||Hello,
Perhaps you should also look "out-of-the-box" and take a look at some other
free database systems that do not impose these ridiculous limits such as
1cpu and no SQL Agent.
Primarily, PostgreSQL and Firebird.
"calderara" <calderara@.discussions.microsoft.com> wrote in message
news:49AE1207-0D8F-4166-8B8E-7FF970F39212@.microsoft.com...[vbcol=seagreen]
> Thanks andrea, its clear now
> "Andrea Montanari" wrote:

MSDE 2000 or SQL Server 2005 Express (Beta) for new project?

Hello guys! I have to develop a new web based project. It's a webportal for events. At the moment it's runnung on an Access database.The new version should be running on a SQL server - the desicion is:MSDE 2000 or SQL Server 2005 Express (Beta). What do you recommend? Thewebpages are developed under .NET 1.1.
SQL Server 2005 Express is not going to be as stable and is not aproven technology as is MSDE. But if your release date somewhatdistant (several months), you may want to use it (hopefully the RTMversion will be relased before you finish.) You'll still be anearly adopter, though, and may have to deal with bugs. In theend, it's a question of: What features do you need in Express that MSDEdoesn't provide? And do these features counter-balance the issuesof working with a beta?
|||Well ... it's a company philosophy to work always on the newsestplattform. If you are common with the MSDE and the SQL Express 2005edition you can surly say if there are some performance improvements.The project leaders think that the MSDE version is not so fast. Specialfeatures are not requested, only SQL querys and stored procedures (...and performance ). Is a change of database engine (from MSDEto SQL 2005) a problem in the future?
Thanks a lot!!!
|||

Here my first look at SQL Server 2005, an events web site needs Time Interval, it is built in SQL server 2005 and index Column include without Composite index. It also schreds and decomposes XML native. Hope this helps.

SQL SERVER 2005 Development

What is new for ASP.NET

The most important is CLR integration write your stored procedures in C#.NET and VB.NET.

INDEX COLUMN INCLUDE, NEW DRI(Declarative Referential Integrity) CASCADE DELETE SET NULL AND CASCADE UPDATE SET NULL, When used with Portal Templates allow the user to browse before login. This is almost like Denormalization with Composite index without the Primary Key restriction of NOT NULL. ANSI NULL enabling on index columns.

Varchar (max), Nvarchar(max) Varbinary(max) Variable length data that may exceed 8000 and 4000 with 2gig limit, in the past these are stored in Text and Image, SQL Server creates an

Arithmetic pointer to the data because it is not table row based.

DTS is now Integration Service with pipeline.

Service Broker can be used to Queue shipping data while SQL Server will process sales Transactions.

XML DATATYPE

XML native Datatypes including XML indexes and XML decomposition.

XML QUERY EXAMPLE using XML PATH

SELECT CustomerID as "@.CustomerID",

(SELECT OrderID as "@.OrderID"

FROM Orders

WHERE Orders.CustomerID = Customers.CustomerID

FOR XML PATH('Order'), TYPE),

(SELECT DISTINCT LastName as "@.LastName"

FROM Employees

JOIN Orders ON Orders.EmployeeID = Employees.EmployeeID

WHERE Customers.CustomerID = Orders.CustomerID

FOR XML PATH('Employee'), TYPE)

FROM Customers

FOR XML PATH('Customer')

COMMON TABLE EXPRESSIONS CTE VIRTIUAL VIEWS

VIEWS are Query Rewrites in ANSI SQL

ANSI SQL 99 with Recursive QUERY Implementation some restrictions.

Tables must be equal INNER JOIN

CONVERT clause can be used to meet the UNION operator requirement.

But multiple Recursive members can only be connected by UNION ALL not UNION because UNION removes duplicates just like SELECT DISTINCT .

Recursion Control

Default server wide - 100

Configurable maximum iterations

OPTION MAXRECURSION <value>

1-32767

Recursive Member Restrictions

No operations leading to DISTINCT

Only UNION ALL allowed between anchor and recursive

SELECT DISTINCT

GROUP BY

HAVING

Scalar Aggregation

TOP

Outer Joins

1 CTE reference per recursive member

The example below in the executing statement, the CTE is referenced twice; that is the reason for the OUTER JOIN, the OUTER JOIN is not allowed with Recursive CTE because in ANSI SQL OUTER JOIN has a default NULL condition and is limited to four iterations while a Recursive CTE can run to 100.

USE AdventureWorks;

GO

WITH Sales_CTE (SalesPersonID, NumberOfOrders, MaxDate)

AS

(

SELECT SalesPersonID, COUNT(*), MAX(OrderDate)

FROM Sales.SalesOrderHeader

GROUP BY SalesPersonID

)

SELECT E.EmployeeID, OS.NumberOfOrders, OS.MaxDate,

E.ManagerID, OM.NumberOfOrders, OM.MaxDate

FROM HumanResources.Employee AS E

JOIN Sales_CTE AS OS

ON E.EmployeeID = OS.SalesPersonID

LEFT OUTER JOIN Sales_CTE AS OM

ON E.ManagerID = OM.SalesPersonID

ORDER BY E.EmployeeID;

GO

Recursive CTE using CONVERT clause to satisfy the UNION ALL operator requirement.

USE AdventureWorks ;

Go

WITH DirectReports(Name, Title, EmployeeID, EmployeeLevel, Sort)

AS (SELECT CONVERT(Varchar(255), c.FirstName + ' ' + c.LastName),

e.Title,

e.EmployeeID,

1,

CONVERT(Varchar(255), c.FirstName + ' ' + c.LastName)

FROM HumanResources.Employee AS e

JOIN Person.Contact AS c ON e.ContactID = c.ContactID

WHERE e.ManagerID IS NULL

UNION ALL

SELECT CONVERT(Varchar(255), REPLICATE ('| ' , EmployeeLevel) +

c.FirstName + ' ' + c.LastName),

e.Title,

e.EmployeeID,

EmployeeLevel + 1,

CONVERT (Varchar(255), RTRIM(Sort) + '| ' + FirstName + ' ' +

LastName)

FROM HumanResources.Employee as e

JOIN Person.Contact AS c ON e.ContactID = c.ContactID

JOIN DirectReports AS d ON e.ManagerID = d.EmployeeID

)

SELECT EmployeeID, Name, Title, EmployeeLevel

FROM DirectReports

ORDER BY Sort ;

GO

The following example is using MAXRECURSION to cancel a statement.

USE AdventureWorks ;

GO

WITH DirectReports(ManagerID, EmployeeID, EmployeeLevel) AS

(

SELECT ManagerID, EmployeeID, 0 AS EmployeeLevel

FROM HumanResources.Employee

WHERE ManagerID IS NULL

UNION ALL

SELECT e.ManagerID, e.EmployeeID, EmployeeLevel + 1

FROM HumanResources.Employee e

INNER JOIN DirectReports d

ON e.ManagerID = d.EmployeeID

)

SELECT *

FROM DirectReports

OPTION (MAXRECURSION 4) ;

GO

First look at SQL Server 2005 development. Comments appreciated.

MSDE 2000 on a Domain Controller

Hello everyone, I have searched the forum regarding this topic and have found numerous good threads about installing SQL Express on a DC. My question is, I am assuming that if installing SQL Express on a Domain Controller is not recommended, that installing the MSDE 2000 on a Domain Controller is not recommended either?

Thanks in advance to all replies!

Tim

Yes, it is not recommended.

However, Microsoft Small Business Server does make an exception and install MSDE (previous versions of SBS) or SQL Express on the DC.

The primary reason for the current recommendation is due to traffic. For MSDE, it was for security and traffic.

|||

Thanks Arnie, that is what I thought.

Tim

MSDE 2000 and SQL2005

I have to install MSDE 2000 with a backup application (CommVault Express
6.1) that does not yet support SQL 2005. I also need to install 2005 for
apps that will utilize this version. Are there any known problems with
running both of these versions of SQL on the same server?
Thanks,
Mark B.I have installed 2000 & 2005 on the same server before and they both work.
The 2000 install is the default instance and the 2005 is the named instance.
The only issue might be whether your server has enough resources to handle
both. Memory in particular. I don't think that both instaces share the same
memory space so you would have to make sure there is enough for both.
"Mark Bohlsen" wrote:
> I have to install MSDE 2000 with a backup application (CommVault Express
> 6.1) that does not yet support SQL 2005. I also need to install 2005 for
> apps that will utilize this version. Are there any known problems with
> running both of these versions of SQL on the same server?
> Thanks,
> Mark B.
>
>|||Yes, I agree with Michael. SQL Server 2000 including MSDE2000 can coexist
with SQL Server 2005 instances on the same computer. Considering SQL Server
performance, your computer may need much more memory and disk space for the
coexistance.
Please feel free to let us know if you need further assistance. Have a good
day!
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||What about MSDE 2000 and SQL 2000 on the same server? Almost every website I
read on this topic says something different.
I have a server that currently runs two named instances of MSDE 2000 SP3a.
I want to install SQL2000 (as the default instance) on the server (the server
is light duty, but has 3GB of RAM). I'd imagine I could upgrade the MSDE
databases to SQL 2000 first, but I rather not since the MSDE instances are
working fine.
- Kevin
"Charles Wang[MSFT]" wrote:
> Yes, I agree with Michael. SQL Server 2000 including MSDE2000 can coexist
> with SQL Server 2005 instances on the same computer. Considering SQL Server
> performance, your computer may need much more memory and disk space for the
> coexistance.
> Please feel free to let us know if you need further assistance. Have a good
> day!
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> =====================================================> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ======================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================>
>

MSDE 2000 and SQL 2005 Express on the same machine

Hi I would like to ask If its possible to have installed MSDE 2000 and SQL 2005 Express on the same machine. My computer uses MSDE 2000 for one application and I would like to install SQL 2005 Express for my own application. I would like to ask it will be a problem before I install it.
thanks a lot
Martin Molnar

No, there should be no interoperability problems. You should be able to install them side-by-side.

Jens K. Suessmeyer

http://www.sqlserver2005.de

MSDE 2000 and SQL 2005 Express on one machine

Is it possible to have these two services on one machine? I notice that my
server requires MSDE 2000 SP3a and don't know it there will be a conflict if
I will install it (or is it possible to have these on the same machine) or I
will just install the 2005 version since it was the replacement of MSDE.
Hoping for your response.
Me
I don't believe you can install both at the same time, at least using
the default installs. 2005 Express attempts to upgrade MSDE
|||I'm running MSDE as the default instance and a SQLEXPRESS
instance on the same machine.
Karl Tarbet
MCSD .net
sql

MSDE 2000 and SQL 2005 Express on one machine

Is it possible to have these two services on one machine? I notice that my
server requires MSDE 2000 SP3a and don't know it there will be a conflict if
I will install it (or is it possible to have these on the same machine) or I
will just install the 2005 version since it was the replacement of MSDE.
Hoping for your response.
MeI don't believe you can install both at the same time, at least using
the default installs. 2005 Express attempts to upgrade MSDE|||I'm running MSDE as the default instance and a SQLEXPRESS
instance on the same machine.
--
Karl Tarbet
MCSD .net

MSDE 2000 and SQL 2005 Express on one machine

Is it possible to have these two services on one machine? I notice that my
server requires MSDE 2000 SP3a and don't know it there will be a conflict if
I will install it (or is it possible to have these on the same machine) or I
will just install the 2005 version since it was the replacement of MSDE.
Hoping for your response.
MeI don't believe you can install both at the same time, at least using
the default installs. 2005 Express attempts to upgrade MSDE|||I'm running MSDE as the default instance and a SQLEXPRESS
instance on the same machine.
Karl Tarbet
MCSD .net

Msde 2000 - Sql 2005 Express Upgrade Issue.

Hey, This is my first time posting here but here goes nothing...

Ok I upgraded an xp machine running to sql express 2005 by doing the inplace upgrade. The upgrade process went great, after the upgrade I could connect to the databases that had been upgraded using the management studio.

BUT.

When I try to connect to the databases using the third party software which had always worked in the past I get the error when trying to access from both the client and server machines.

[DBNETLIB][Connection open()).]SQL Server does not exist or access denied.

I then tried setting up SQL express 2005 on another xp station just to test how things worked if it wasn't an upgrade. I installed, attached the databases (which I copied to that local machine) and I was able to connect to them through the third party software from the server machine, but not client machines. The client machines gave me the same error as above.

Does anyone have any ideas, I have been talking to the third party support but haven't gotten any where yet... does anyone have any suggestions?

Thanks,why would you want to upgrade from MSDE 2000 to SQL 2005 express? Microsoft has stated more than 80% of the application running on SQL 2000 will not work on SQL 2005. Why not using the same old MSDE 2000?

most probably you will need to rewrite your application to handle SQL 2005|||I spoke with the third party software company and they assure me everything will work on sql express. We wanted to switch to sql express because it had the report server stuff built in. I don't really know that much about this stuff, can the sql 2005 express reporting stuff be run on msde ?|||I am not the expert here but I will just share what I have experienced so far.

Report server is a built in feature in SQL 2005. However, it has its limitation when it comes to report designer. My personal experience, it's easy to use, but it's not acceptable by the end user. I end up writing my own long script to output the whole report to excel file.

You shall show your users instead of simply pushing them to another technology. MSDE can run well on WinXP, so why change? If you can't give yourself a good reason to change, it's better to stick to something that's working.

Remember, free stuff, doesn't come in handy :D unless your requirement is very very simple.

If the software vendor assure you that, ask them to show you how to migrate the thing over. You can always use VMware or Parallels to do all the testing before you screw up your MSDE.|||Thanks for the insight with the reporting stuff. Do you know if the report stuff from express can be used with msde?

Also, I think it's to late for me on the screwing up the msde. I removed sql express now and I have reinstalled msde, but I am getting the same error I was getting with the express. I have done a little reading and it seems like it might be a problem with remote connections. Does anyone know how to make sure remote connections are allowed in msde ?sql

MSDE / SQL Server 2005 express

Is it possible to install both MSDE and SQL Server 2005 express on the same
XP Pro machine?
Thanks
hi,
Bamboozled wrote:
> Is it possible to install both MSDE and SQL Server 2005 express on
> the same XP Pro machine?
>
yes it is...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE / SQL Express Question

what is the limitation in terms of connections? I've read something along
the lines of 5-10 connections?MSDE had a 5 concurrent connection 'governor. With SQL Server 2005 Express,
the governor has been removed, and the limit is mostly related to the type
of activity and hardware. Of course, there will be some relationship with
and processor/memory/disk subsystem -up to the limits.
With low to moderate frequency activity (small packets) in a small OLTP
database, you might be able to adequately support 20-30 users. Large
resultsets in a OLAP may only support 1-5 users. Plan to thoroughly test any
implementation.
See specifications at:
http://www.microsoft.com/sql/prodin...e-features.mspx
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"g" <gregoranton_nospamplease_@.hotmail.com> wrote in message
news:8pIPg.24564$Lb5.16987@.edtnps89...
> what is the limitation in terms of connections? I've read something along
> the lines of 5-10 connections?
>|||On Tue, 19 Sep 2006 02:15:32 GMT, g wrote:

>what is the limitation in terms of connections? I've read something along
>the lines of 5-10 connections?
>
Hi g,
In addition to Arnie's answer: the MSDE workload governor limits
concurrent _WORKLOADS_, not connections. An idle connection is not a
workload, a working connection is. Some connections might even spawn
multiple workloads. So ten, twenty, fifty or even hundred data entry
typists coould all simultaneously be connected to MSDE without ever
hitting the 5-workload limit. But one carefully architected procedure
that spawns multiple connections (not easy to do, but possible) could
bring MSDE to it's knees all by itself.
Oh, and if you surpass the maximum of 5 concurrent workloads, the effect
will be that the workload governor starts to throttle performance. A bit
if you have only 6 workloads, but progressively more as the number of
workloads increases - effectively, MSDE will slow down to an almost halt
if you keep increasing concurrent workloads.
Hugo Kornelis, SQL Server MVP

MSDE / SQL Express Question

what is the limitation in terms of connections? I've read something along
the lines of 5-10 connections?
MSDE had a 5 concurrent connection 'governor. With SQL Server 2005 Express,
the governor has been removed, and the limit is mostly related to the type
of activity and hardware. Of course, there will be some relationship with
and processor/memory/disk subsystem -up to the limits.
With low to moderate frequency activity (small packets) in a small OLTP
database, you might be able to adequately support 20-30 users. Large
resultsets in a OLAP may only support 1-5 users. Plan to thoroughly test any
implementation.
See specifications at:
http://www.microsoft.com/sql/prodinf...-features.mspx
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"g" <gregoranton_nospamplease_@.hotmail.com> wrote in message
news:8pIPg.24564$Lb5.16987@.edtnps89...
> what is the limitation in terms of connections? I've read something along
> the lines of 5-10 connections?
>
|||On Tue, 19 Sep 2006 02:15:32 GMT, g wrote:

>what is the limitation in terms of connections? I've read something along
>the lines of 5-10 connections?
>
Hi g,
In addition to Arnie's answer: the MSDE workload governor limits
concurrent _WORKLOADS_, not connections. An idle connection is not a
workload, a working connection is. Some connections might even spawn
multiple workloads. So ten, twenty, fifty or even hundred data entry
typists coould all simultaneously be connected to MSDE without ever
hitting the 5-workload limit. But one carefully architected procedure
that spawns multiple connections (not easy to do, but possible) could
bring MSDE to it's knees all by itself.
Oh, and if you surpass the maximum of 5 concurrent workloads, the effect
will be that the workload governor starts to throttle performance. A bit
if you have only 6 workloads, but progressively more as the number of
workloads increases - effectively, MSDE will slow down to an almost halt
if you keep increasing concurrent workloads.
Hugo Kornelis, SQL Server MVP

MSDE / SQL Express Question

what is the limitation in terms of connections? I've read something along
the lines of 5-10 connections?MSDE had a 5 concurrent connection 'governor. With SQL Server 2005 Express,
the governor has been removed, and the limit is mostly related to the type
of activity and hardware. Of course, there will be some relationship with
and processor/memory/disk subsystem -up to the limits.
With low to moderate frequency activity (small packets) in a small OLTP
database, you might be able to adequately support 20-30 users. Large
resultsets in a OLAP may only support 1-5 users. Plan to thoroughly test any
implementation.
See specifications at:
http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"g" <gregoranton_nospamplease_@.hotmail.com> wrote in message
news:8pIPg.24564$Lb5.16987@.edtnps89...
> what is the limitation in terms of connections? I've read something along
> the lines of 5-10 connections?
>|||On Tue, 19 Sep 2006 02:15:32 GMT, g wrote:
>what is the limitation in terms of connections? I've read something along
>the lines of 5-10 connections?
>
Hi g,
In addition to Arnie's answer: the MSDE workload governor limits
concurrent _WORKLOADS_, not connections. An idle connection is not a
workload, a working connection is. Some connections might even spawn
multiple workloads. So ten, twenty, fifty or even hundred data entry
typists coould all simultaneously be connected to MSDE without ever
hitting the 5-workload limit. But one carefully architected procedure
that spawns multiple connections (not easy to do, but possible) could
bring MSDE to it's knees all by itself.
Oh, and if you surpass the maximum of 5 concurrent workloads, the effect
will be that the workload governor starts to throttle performance. A bit
if you have only 6 workloads, but progressively more as the number of
workloads increases - effectively, MSDE will slow down to an almost halt
if you keep increasing concurrent workloads.
--
Hugo Kornelis, SQL Server MVP

MSDE -> SQL2005Express

Hello, Can I upgrade MSDE to SQL2005 Express without lost any DB.
Thank you very much for help.
Best regards
hi,
Petr Jirman wrote:
> Hello, Can I upgrade MSDE to SQL2005 Express without lost any DB.
> Thank you very much for help.
> Best regards
yes, you can .. http://msdn2.microsoft.com/en-us/library/ms143393.aspx
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply
|||Hello,
There will not be any data loss.
1. Install SQL Express
2. Backup the databases in MSDE
3. Restore the backup in SQL Express.
Thanks
Hari
"Petr Jirman" <PetrJirman@.discussions.microsoft.com> wrote in message
news:183A89E5-48F3-4A58-9D91-327DC3FFEA15@.microsoft.com...
> Hello, Can I upgrade MSDE to SQL2005 Express without lost any DB.
> Thank you very much for help.
> Best regards
|||Hi, thank you
PLS Do you know how can I make upgrade ? I would like upgrade with CMD
command. I have 263 instance of MSDE and I cannot say the SA password to any
other peaple (they is only PC worker).
"Andrea Montanari" wrote:

> hi,
> Petr Jirman wrote:
> yes, you can .. http://msdn2.microsoft.com/en-us/library/ms143393.aspx
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
> -- remove DMO to reply
>
>
|||hi,
Petr Jirman wrote:
> Hi, thank you
> PLS Do you know how can I make upgrade ? I would like upgrade with CMD
> command. I have 263 instance of MSDE and I cannot say the SA password
> to any other peaple (they is only PC worker).
aghhh!!!
you could prepare a "setting" file that will "include" the "secret" sa pwd
to be consumed so that you only have to burn a cd with SQLExpress installer
and the setting ini file and perform, for each computer, the required
installation.. the installer must be called, in that scenario, including the
setting file parameter..
or you can include in the cd a batch file calling the installer with all
required parameters..
you can have a look at all supported parameters at
http://msdn2.microsoft.com/en-us/library/ms144259.aspx, including setting's
ini file ...
when finished you have to trash the cd :D
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply
|||Consider that when you convert your MSDE (SQL Server 2000) by attaching the
..MDF file to a SQL Server 2005 Express master database, the file itself will
be morphed and made unreadable by MSDE. When the conversion is done, the
database compatibility level will be set to 8.0 (SQL Server 2000) so most of
the SQL Server 2005 features won't work against the newly converted
database. To correct this, you'll need to use SQL Server Enterprise Manager
Express to change the Compatibility Level to 9.0. When you do the engine
scrubs the database looking for issues that you might need to correct before
it can be fully 9.0 (SQL Server 2005) compatible.
I discuss these issues in more detail in my book.
hth
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest books:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition) and
Hitchhiker's Guide to SQL Server 2005 Compact Edition
------
"Petr Jirman" <PetrJirman@.discussions.microsoft.com> wrote in message
news:183A89E5-48F3-4A58-9D91-327DC3FFEA15@.microsoft.com...
> Hello, Can I upgrade MSDE to SQL2005 Express without lost any DB.
> Thank you very much for help.
> Best regards

MSDE > SQL Express

We have a product on the market, with 100k or so installs that use MSDE as its database (desktop application in .net). Our number 1 complaint is massive installation problems with MSDE.

Now, we are stuck a bit - first, we need to release a Vista Compatible version - which means no MSDE. We also need to migrate users from MSDE to SQL Express, with no data loss (we deal with financial information, and people tend to have zero tolerance for data loss here).

So, I have large scale reservations for two reasons - first, Microsoft's track record in supporting and making MSDE in the past has not been stellar.

With that said - are the multiple installation failure issues fixed in SQL Express? Did MS make the effort to get SQL Express to install on Win2k/XP/Vista improved? Are their benchmark figures out there regarding SQL Express install failure rates?

Additionally, can I get some information regarding MSDE to SQL Express upgrades done during for existing customers?

jason

Hi Jason,

Great strides have been made in installation for SQL Express and it is much better than MSDE. This is not to say there are no issues, a quick search of this forum will confirm that there are, but I have not seen the kind of wholesale failures that were common with MSDE. I think SQL Express is way better for install than MSDE.

I don't know of anyone that tracks benchmarks such as you describe, sorry. I can point you to an article that we have that describes best practices for upgrading from MSDE to SQL Express, you can find it here. I have confidence that our upgrade procedure will not harm or lose our data since your database files are just left in place and then attached once the new server is installed, but I would be remise to not remind you that you should take responsibility for protecting your own important data.

I'd say that it's critical to backup your databases as a first step of any migration process. Additionally, you may want to consider doing a side by side upgrade in stead of in place to give you maximum control. During a side by side upgrade, you manually move your databases, so you can choose to use a copy (leaving the original safe) or even migrate your data by restoring a backup rather than using the original mdf. One thing to remember, once the database is converted to SQL 2005, it can't go back to 2000 format. If you are concerned that you might want to roll back the migration, you need to ensure that you keep a copy of the 2000 format database around until migration is complete.

Mike

MSDE -> Express Upgrade problem.

Hello!

I'm trying to upgrade old MSDE instances to SQL Server 2005 Express SP1.

The following command fails:
SQLEXPR.EXE /qb UPGRADE=SQL_Engine INSTANCENAME=XXX ADDLOCAL=Client_Components,Connectivity

because the domain\x user cannot login. We have disabled Windows authentication. Is there a way to supply the SA login instead of a domain user?

Problem no #2:
After upgrading with Windows Authentication turned on, current SQL users cannot login (sa). Is Mixed authentication mode turned off during upgrade? Or what else could be the problem?

Our application is distributed around Europe. We have no control over our customers security settings/logins.
Also, the database contains sensitive data. Giving Windows Administrators access to the database is out of the question.

Kind regards

A

Check in the template.ini file that's in the high-level directory of the install media; the options are explained pretty well in there but in brief you can specify accounts, passwords, and security mode.

MSDE & SQL Express use?

I know this may have been asked in the past, and I've tried to search the forum, but didn't find any clear responses.

The question is about MSDE and SQL Express being "Free".

Can MSDE or SQL Server express be used for the backend DB for an application for a private (for profit) company? A COTS that we are planning to puchase can work with either commercial version of SQL server or MSDE / Express. Any input would be appreciated.

Thank you,

Yes - absolutely free, even for commercial use. But use Express - MSDE has a query governor, Express doesn't.

If this post answers your question, make sure you mark it "answered" so others can find it quickly.

Thanks -

Buck Woody
http://www.buckwoody.com

|||Hi,

I don′t know what COTS means, but they are both free for use. You can use them within your applications. There are limitations on the free versions which you might encounter in the future. But its quite easy to "migrate" from the free versions to the full blown versions of SQL Server.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de