Other applications using MSDE

What other applications outside Microsoft products, use MSDE?
Hi,
You're asking a question here that isn't possible to answer. There are a
huge number of software vendors that now use the MSDE as one of their forms
of deployment. A large percentage of SQL Server based applications could be
deployed against the MSDE at the lower end of the market. It's a similar
question to asking "What other applications outside Microsoft products, use
SQL Server?".
Sorry there isn't a simple answer.
HTH,
Greg Low (MVP)
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Moj_Sharp Labs" <anonymous@.discussions.microsoft.com> wrote in message
news:D1298C09-2F40-4CBA-86F7-96BA7DC09CC5@.microsoft.com...
> What other applications outside Microsoft products, use MSDE?
|||sourcegear's version control system, vault, integrates with msde for
smaller based development shops which do not want to purchase a full sql
server license.
http://www.sourcegear.com/vault/
jeff clausius
sourcegear
"=?Utf-8?B?TW9qX1NoYXJwIExhYnM=?=" <anonymous@.discussions.microsoft.com>
wrote in news:D1298C09-2F40-4CBA-86F7-96BA7DC09CC5@.microsoft.com:

> What other applications outside Microsoft products, use MSDE?

OSQL and SQL 2005 Express

Hi All... I'm trying to upgrade one of our MSDE-based products to SQL 2005 Express. The installation of the product includes the use of a bat file that makes several OSQL calls. This bat file runs on the machine that has SQL 2005 Express installed and is failing - times out trying to connect. I've gotten away from the bat file and am now just trying to run OSQL against the db from a dos prompt. I'm getting the following:

C:\Documents and Settings\cdehaven>osql -E
[SQL Native Client]Named Pipes Provider: Could not open a connection to SQLServer [2].
[SQL Native Client]Login timeout expired
[SQL Native Client]An error has occurred while establishing a connection to
the server. When connecting to SQL Server 2005, this failure may be caused by
the fact that under the default settings SQL Server does not allow remote
connections.

Any thoughts? Thanks much!!

Curt

Answered my own question! I added a switch to the OSQL command line:

-S.\sqlexpress

This specifies the server and i suppose instance of sql server to connect to. I never needed to do this with MSDE, but I guess we need to now...

Curt

|||

MSDE installed as a default instance by default, SQL Server 2005 does not, it installs the Express instance by default in Machine\SQLExpress. if you are using a named instance you will either have to provide the following syntax (or use a SQLAlias on the machines)

1. Machine\InstanceName
2 Machinename,Portnumber (Which will redirect to the named instance, be aware that this is impratical for SQL Server Express named instances by default as the port is dynamically choosenupon startup of the service)

Jens K. Suessmeyer

http://www.sqlserver2005.de