Deployment Toolkit worth using?

I want to deploy a VB.NET app along with MSDE and a sample database.
I've been trying to use the MSDE Deployment Toolkit, with help from
Mario Szpuszta's 3/04 article on MSDN. However, the article does not
include sample code, nor can I find it on the web - all the links I've
located are dead, and Szpuszta seems to have dropped off the face of
the earth. (The samples that come with the kit are NOT the code
Szpuszta refers to in the article.)
I've put together enough of Szpuszta's sample to install the framework
and MSDE as needed, but I can't get the database deployed. The article
leaves out a lot of critical info, so I'd be glad to have the sample
solution he uses.
I guess my real question at this point is: am I wasting my time? Maybe
there's a newer, more preferred way of solving the problem by now. Any
thoughts?
I'll post my own reply, for those who might want it. I located Mario's
blog and sent him a message. He replied with a link to the source for
his demonstration solution (VB.NET). I won't post the whole ugly link -
just go to GotDotNet/UserSamples and search on "MSDE".
MSDE Deployment Toolkit in Action - Sample Files

Deployment on MSDE

Hi All,
Is it possible to use SQL Server 2000 Developer Edition for development and then deploy the database on MSDE?
Regards.
hi sm,
"sm" <sm@.discussions.microsoft.com> ha scritto nel messaggio
news:1143B7F5-D2C5-42B9-8C24-3E21589830C2@.microsoft.com...
> Hi All,
> Is it possible to use SQL Server 2000 Developer Edition for development
and then
>deploy the database on MSDE?
this is usually the solution to go...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Deployment of system

I am about to start developing a system using VB 2003 and SQL Server 2000. On my development computer, I am going to use MSDE for the database, which I guess I will later be able to export to my client's SQL server 2000.

Now, I am a bit worried. In my local computer, I can develop a system which runs locally very well. So, I am very sure I will be able to develop one for my client. But when I later deploy it to the client, it will have to run on a server and client machines.

My question is, how easy or complex is it to deploy such a system from my standalone platform to a client-server one. I have adequate experience developing stand-alone systems.

I am about to get started so please kindly give me ideas on the best path to take.

Hi there and welcome to client server development :-)

Its quite easy if you are developing on a MSDE and want to deploy that later on a Std / Ent Server. It is reduced to making a backup and restoring the backup on the server, normally that should be all except for the server users, which additionally have to be scripted and deployed.

BTW: If you want to deploy it on productional systems on Std / Ent Editions, why don′t you use SQL Server Dev Edition to develop the applications. It would be more comfortable for you and it would be a more soution-near development.

HTH, jens Suessmeyer.

http://www.sqlserver2005.de

|||

Thanx a lot for the info.

What I am about to develop is really a small system that would not warrant me going for any extra development tools more than what I have - cost is an issue.

You said that the database it is a matter of backup/restore. What about the VB application? Lets take the simplest example below.

Supposing I have a VB form bound to a datasource coming from some SQL Connection (localhost) on my development PC. The form will run on my computer because its connection is there.

Now, what happens if I take the above (app and database) to client-server environment. I restore the db on server and install app on client (?). But the connection in app is to localhost on my development PC. So it will not run in client-server until I modify the connection to point to the new server. Am I right or wrong?

|||Hi,

yes you are right, but that a point of configuration. I think right now you are using configurable settings in your application, so just add another setting to pass the servername, port etc. to the data source creator (or whatever you implemented).

The developer edition isn′t expensive at all. Should be available for 49$ (around),so developing on development edition will help you in many cases spending (/wasting) time for configuring something or getting a fst info from the server.

HTH, jens Suessmeyer.

http://www.sqlserver2005.de
|||Be blessed. I'll check out all your suggestions.

Deployment of MSDE

Is there a way to turn off System Administrators in Server Roles for the
Builtin\Administrators using the deployment toolkit?
No
"Jon" <Jon@.discussions.microsoft.com> wrote in message
news:1364DDFA-764B-4C65-AC14-BBBFEB979DD2@.microsoft.com...
> Is there a way to turn off System Administrators in Server Roles for the
> Builtin\Administrators using the deployment toolkit?
|||Hi Jon,
I install MSDE with my C# app via the deployment toolkit.
As soon as my C# app starts, I run the command against the DB
EXEC sp_denylogin [BUILTIN\\Administrators]
This removes the admins from the built in group
HTH
Paul
"Jon" <Jon@.discussions.microsoft.com> wrote in message
news:1364DDFA-764B-4C65-AC14-BBBFEB979DD2@.microsoft.com...
> Is there a way to turn off System Administrators in Server Roles for the
> Builtin\Administrators using the deployment toolkit?
|||hi Paul,
Paul Aspinall wrote:
> Hi Jon,
> I install MSDE with my C# app via the deployment toolkit.
> As soon as my C# app starts, I run the command against the DB
> EXEC sp_denylogin [BUILTIN\\Administrators]
> This removes the admins from the built in group
>
and the SQL Server Agent can run without problems?
(http://support.microsoft.com/default.aspx?kbid=237604)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
sql

Deployment for a small office

Hi,
I am creating a shrinkwrap winapp using vb.net which uses MSDE for backend. I have used the MSDE deployment toolkit to deploy MSDE along with the app. Everything works fine when the db and the app are on the same machine. I just install MSDE with named
instance for my company, create database and start the service. Even backup/restore work fine.
Now, my confusion is to how to make all this work for a small office where the setup will be like this (For e.g.):
1> 4 pcs (win xp) where my app will be installed to be used by 4 different users.
2> 1 central pc A (can be win xp) where the database is.
3> All 4 users want to share my database which is on the central pc A.
So, my concerns are:
1> How will the setup and deployment change.
2> Will the MSDE deployment toolkit still work.
3> Will I need to install myapp + MSDE on client's machine or just myapp.
4> What will I have to install on the central pc A.
5> Right now my connection string is like this:
data source=(local)\MyInstanceName;initial catalog=MyDB; User id =MyUser; Password=MyPassword
How will this change when the Db is on the central machine A.
6> If I use DMO, then what extra will I need to install on the 4 pcs and the central machine A.
Thanks
dev
hi dev_kh,
"dev_kh" <devkh@.discussions.microsoft.com> ha scritto nel messaggio
news:9D43D477-50C4-47DE-8174-CE196F5BD683@.microsoft.com...
> ...
> So, my concerns are:
> 1> How will the setup and deployment change.
your setup shoul'd ask for MSDE installation, app installation or both...
you can even install MSDE on all client PCs, but they will not be used, or
shall not..

> 2> Will the MSDE deployment toolkit still work.
don't know.. never used :-(

> 3> Will I need to install myapp + MSDE on client's machine or just myapp.
see >1>

> 4> What will I have to install on the central pc A.
it depends... MSDE for sure, but il the server will actually works as a user
client too [as usal for small offices :-( ] you have to install your app
too..

> 5> Right now my connection string is like this:
> data source=(local)\MyInstanceName;initial catalog=MyDB; User id =MyUser;
>Password=MyPassword
> How will this change when the Db is on the central machine A.
data source=ServerComputerName\MyInstanceName;initial catalog=MyDB; User id
=MyUser; Password=MyPassword

> 6> If I use DMO, then what extra will I need to install on the 4 pcs and
the central machine A.
con the server PC you have to install nothing, as SQL-DMO is included in
MSDE package...
on all 4 client PCs, you have to install SQL-DMO component and
dependencies...
the complete dependency list is as above:
; not licensed by redist.txt but available after installation of MDAC2.6
...\WINDOWS\SYSTEM\odbcbcp.dll; DestDir: WinSys ; sharedfile
; not licensed by redist.txt but available after installation of MDAC2.6
...\WINDOWS\SYSTEM\sqlwoa.dll ; DestDir: WinSys
; not licensed by redist.txt but available after installation of MDAC2.6
...\WINDOWS\SYSTEM\sqlwid.dll ; DestDir: WinSys
...\Programmi\Microsoft SQL Server\80\Tools\Binn\w95scm.dll; DestDir:
DestinationFolder\Binn
...\WINDOWS\SYSTEM\sqlunirl.dll ; DestDir: WinSys
...\Programmi\Microsoft SQL Server\80\Tools\Binn\sqlresld.dll; DestDir:
DestinationFolder\Binn
...\Programmi\Microsoft SQL Server\80\Tools\Binn\sqlsvc.dll; DestDir:
DestinationFolder\Binn
; not licensed by redist.txt but available after installation of MDAC2.6
...\Programmi\Microsoft SQL Server\80\Tools\Binn\Resources\1033\sqlsvc.RLL;
DestDir: DestinationFolder\Binn\Resources\1033
; not licensed by redist.txt but available after installation of MDAC2.6
...\Programmi\Microsoft SQL Server\80\Tools\Binn\Resources\1033\Sqldmo.rll;
DestDir: DestinationFolder\Binn\Resources\1033
...\Programmi\Microsoft SQL Server\80\Tools\Binn\sqldmo.dll; DestDir:
DestinationFolder\Binn ; file to be registered via regserver
DestinationFolder can either be the installation directory of one instance
of Microsoft SqlServer 2000, like ..\Program Files\Microsoft SQL
Server\80\Tools, even if no istance of SQL Server has been installed, or the
installation directory of your app. Please do respect the hierarchy
\Binn\Resources\1033 (where 1033 specifies the language), where needed, in
order to grant correct functionality of Ole-Automation objects.
In order to install SQL-DMO components for MSDE 2000, Microsoft Internet
Explorer 5.5 or higher is required.
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||See comments inline.
"dev_kh" <devkh@.discussions.microsoft.com> wrote in message
news:9D43D477-50C4-47DE-8174-CE196F5BD683@.microsoft.com...
> Hi,
> I am creating a shrinkwrap winapp using vb.net which uses MSDE for
backend. I have used the MSDE deployment toolkit to deploy MSDE along with
the app. Everything works fine when the db and the app are on the same
machine. I just install MSDE with named instance for my company, create
database and start the service. Even backup/restore work fine.
> Now, my confusion is to how to make all this work for a small office where
the setup will be like this (For e.g.):
> 1> 4 pcs (win xp) where my app will be installed to be used by 4 different
users.
> 2> 1 central pc A (can be win xp) where the database is.
> 3> All 4 users want to share my database which is on the central pc A.
> So, my concerns are:
> 1> How will the setup and deployment change.
I'd prefer seperate installations of MSDE and app to put them in a single
setup procedure, unless the use who does the setup knows nothing but
double-clicking "setup.exe", since most likely, MSDE will be installed on
only one computer on the network while app will be installed on all
computers (of course it may also places on a network share and all computers
only get a shortcut to run it).

> 2> Will the MSDE deployment toolkit still work.
See above.

> 3> Will I need to install myapp + MSDE on client's machine or just myapp.
Install MSED on computer A only. as for app, you can choose install on all
client computers or place it on a sinle network share location. Now that it
is .NET app, of course yu have to make sure all computer has .NET framework
installed; amd also do some security configuration, since app loaded from
other computer is now allowed to run by default, you need to give it
permission to run: go to control panel->MS .NET framework confuguration to
allow the app loaed from other computer to run.
When I put my app in use, very often I know there are quite some bugs
undetected and some fixes are required soon or later, place the app in a
network share allows me just replace file(s) in a single location.

> 4> What will I have to install on the central pc A.
Nothing but MSDE.

> 5> Right now my connection string is like this:
> data source=(local)\MyInstanceName;initial catalog=MyDB; User id =MyUser;
Password=MyPassword
Just change "data source" to computer A's name: "data
source=computerAName\MSDEInstanceName;Initial..."

> How will this change when the Db is on the central machine A.
> 6> If I use DMO, then what extra will I need to install on the 4 pcs and
the central machine A.
You do not need install anything, unless your app uses DMO. DMO is installed
automatically with MSDE. Since MSDE is only installed on one computer, if
your app do require DMO to run, the get DMO on client computer without
install MSDE is quite tricky.
You probably use DMO for a few MSDE management task, like backup/restore.
I'd suggest you seperate this kind of task from your app into a single MSDE
app, which is only installed on the computer A. You do not want every user
to perform MSDE management task, do you?

> Thanks
> dev
|||Great,
So basically, in a small networked office setup I described,I will:
1> Install myapp on all 4 machines
2> Install MSDE on the centralserver A
3> Connection string will point to the machine A for datasource
But what about:
1> If I need to start the sqlserver service on clients machine, for e.g. to backup/restore database. How will I do it. Currently I use the following code to create the service controller and then start it if needed:
svc = New ServiceController("MSSQL$MyInstanceName)
What will I do when the service is on the central machine. How to start the service using the above code.
(See my clients will not have a dba and are assumed to not know that there is anything related to sql server on their machines, so we are providing the UI for backup/restore etc and the db functionality is kept as hidden as possible from them, this UI wil
l be in the tools on my vb.net app)
2> Will I need to run any network config utilities on the client machine. I know I will have to set disablenetworkprotocols to false on the server, but is there anything related to network access to be done on the client.
3> Andrea sometime back you mentioned something like, the location to backup should be from the MSDE machine's point of view.. so if PC1 wants to backup the db on it's D:\Backup drive, then what change will I have to do to this code below(which works fine
for a machine which has msde installed)
'--
cn = New SqlConnection(mMasterConnString)
cn.Open()
Dim cm As New SqlCommand
With cm
.Connection = cn
.CommandType = CommandType.Text
.CommandText = "BACKUP DATABASE " & mDBName & " TO DISK = '" & bkpFileWithPath & "' WITH NAME = My Backup', INIT"
.ExecuteNonQuery()
End With
'Note: bkpFileWithPath argument is: "D:\Backup\MyDB.bak"
'---
4> I guess I will take DMO slowly..
Thanks a lot guys. Hey Andrea do you have a blog?
dev_kh
"Norman Yuan" wrote:

> See comments inline.
> "dev_kh" <devkh@.discussions.microsoft.com> wrote in message
> news:9D43D477-50C4-47DE-8174-CE196F5BD683@.microsoft.com...
> backend. I have used the MSDE deployment toolkit to deploy MSDE along with
> the app. Everything works fine when the db and the app are on the same
> machine. I just install MSDE with named instance for my company, create
> database and start the service. Even backup/restore work fine.
> the setup will be like this (For e.g.):
> users.
> I'd prefer seperate installations of MSDE and app to put them in a single
> setup procedure, unless the use who does the setup knows nothing but
> double-clicking "setup.exe", since most likely, MSDE will be installed on
> only one computer on the network while app will be installed on all
> computers (of course it may also places on a network share and all computers
> only get a shortcut to run it).
>
> See above.
>
> Install MSED on computer A only. as for app, you can choose install on all
> client computers or place it on a sinle network share location. Now that it
> is .NET app, of course yu have to make sure all computer has .NET framework
> installed; amd also do some security configuration, since app loaded from
> other computer is now allowed to run by default, you need to give it
> permission to run: go to control panel->MS .NET framework confuguration to
> allow the app loaed from other computer to run.
> When I put my app in use, very often I know there are quite some bugs
> undetected and some fixes are required soon or later, place the app in a
> network share allows me just replace file(s) in a single location.
>
> Nothing but MSDE.
> Password=MyPassword
> Just change "data source" to computer A's name: "data
> source=computerAName\MSDEInstanceName;Initial..."
> the central machine A.
> You do not need install anything, unless your app uses DMO. DMO is installed
> automatically with MSDE. Since MSDE is only installed on one computer, if
> your app do require DMO to run, the get DMO on client computer without
> install MSDE is quite tricky.
> You probably use DMO for a few MSDE management task, like backup/restore.
> I'd suggest you seperate this kind of task from your app into a single MSDE
> app, which is only installed on the computer A. You do not want every user
> to perform MSDE management task, do you?
>
>
>

Deploying SQL Server 2000 database on MSDE

Hi All,
I have done by development using SQL Server 2000 Developer Edition. How do I deploy the database in MSDE?
Regards.
Hi,
2 Methods
1. Backup the database in SQL 2000 developer edition (Backup DATBASE) and
copy to MSDE machine and Restore it (RESTORE DATABASE)
2. Detach the (SP_DETACH_DB) in SQL 2000 developer edition , copy the MDF
and LDF to MSDE machine and then Attach the database (SP_ATTACH_DB)
See the command usage in books online.
Note:
If your database size is > 2 GB then you cant restore or attach the database
to MSDE. MSDE allows a maximum 2 GB database size.
Thanks
Hari
MCDBA
"sm" <sm@.discussions.microsoft.com> wrote in message
news:2AF7E862-5006-43E8-A828-A6337E7D2870@.microsoft.com...
> Hi All,
> I have done by development using SQL Server 2000 Developer Edition. How do
I deploy the database in MSDE?
> Regards.
|||Thanks.
"Hari Prasad" wrote:

> Hi,
> 2 Methods
> 1. Backup the database in SQL 2000 developer edition (Backup DATBASE) and
> copy to MSDE machine and Restore it (RESTORE DATABASE)
> 2. Detach the (SP_DETACH_DB) in SQL 2000 developer edition , copy the MDF
> and LDF to MSDE machine and then Attach the database (SP_ATTACH_DB)
>
> See the command usage in books online.
> Note:
> If your database size is > 2 GB then you cant restore or attach the database
> to MSDE. MSDE allows a maximum 2 GB database size.
> Thanks
> Hari
> MCDBA
>
> "sm" <sm@.discussions.microsoft.com> wrote in message
> news:2AF7E862-5006-43E8-A828-A6337E7D2870@.microsoft.com...
> I deploy the database in MSDE?
>
>

deploying MSDE instance

Hi there,
I am having a hard time trying finding information on how to deploy my
instance along with my application. I found the following link to be useful
in attaching my database to the server
(http://support.microsoft.com/kb/q240293/) but how do I create that instance
for the attachment to occur. My application was coded using Visual C++ so
the deployment using the VB Package and Deployment Wizard does not apply. I
looked endless on the web on how to do this but to no avail.
I'm using Installshield X to package my install. I have it setup so that the
MSDE install folder is copied onto the c: drive. But I need to create the
instance in the command line using setup.exe. I don't know how to call the
command line within the Installshield script to create my instance. Am I
headed in the wrong direction or is there some easier way? Any help would be
much appreciated!
Hi
These may help!
http://msdn.microsoft.com/library/de...eddingmsde.asp
http://www.microsoft.com/sql/msde/te...ntegration.asp
John
"luv2travel" wrote:

> Hi there,
> I am having a hard time trying finding information on how to deploy my
> instance along with my application. I found the following link to be useful
> in attaching my database to the server
> (http://support.microsoft.com/kb/q240293/) but how do I create that instance
> for the attachment to occur. My application was coded using Visual C++ so
> the deployment using the VB Package and Deployment Wizard does not apply. I
> looked endless on the web on how to do this but to no avail.
> I'm using Installshield X to package my install. I have it setup so that the
> MSDE install folder is copied onto the c: drive. But I need to create the
> instance in the command line using setup.exe. I don't know how to call the
> command line within the Installshield script to create my instance. Am I
> headed in the wrong direction or is there some easier way? Any help would be
> much appreciated!
|||Thanks John!
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> These may help!
> http://msdn.microsoft.com/library/de...eddingmsde.asp
> http://www.microsoft.com/sql/msde/te...ntegration.asp
> John
> "luv2travel" wrote:

deploying MSDE instance

Hi there,
I am having a hard time trying finding information on how to deploy my
instance along with my application. I found the following link to be useful
in attaching my database to the server
(http://support.microsoft.com/kb/q240293/) but how do I create that instance
for the attachment to occur. My application was coded using Visual C++ so
the deployment using the VB Package and Deployment Wizard does not apply. I
looked endless on the web on how to do this but to no avail.
I'm using Installshield X to package my install. I have it setup so that the
MSDE install folder is copied onto the c: drive. But I need to create the
instance in the command line using setup.exe. I don't know how to call the
command line within the Installshield script to create my instance. Am I
headed in the wrong direction or is there some easier way? Any help would be
much appreciated!Hi
These may help!
http://msdn.microsoft.com/library/d...beddingmsde.asp
http://www.microsoft.com/sql/msde/t...integration.asp
John
"luv2travel" wrote:

> Hi there,
> I am having a hard time trying finding information on how to deploy my
> instance along with my application. I found the following link to be usefu
l
> in attaching my database to the server
> (http://support.microsoft.com/kb/q240293/) but how do I create that instan
ce
> for the attachment to occur. My application was coded using Visual C++ so
> the deployment using the VB Package and Deployment Wizard does not apply.
I
> looked endless on the web on how to do this but to no avail.
> I'm using Installshield X to package my install. I have it setup so that t
he
> MSDE install folder is copied onto the c: drive. But I need to create the
> instance in the command line using setup.exe. I don't know how to call the
> command line within the Installshield script to create my instance. Am I
> headed in the wrong direction or is there some easier way? Any help would
be
> much appreciated!|||Thanks John!
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> These may help!
> http://msdn.microsoft.com/library/d...beddingmsde.asp
> http://www.microsoft.com/sql/msde/t...integration.asp
> John
> "luv2travel" wrote:
>

deploying MSDE instance

Hi there,
I am having a hard time trying finding information on how to deploy my
instance along with my application. I found the following link to be useful
in attaching my database to the server
(http://support.microsoft.com/kb/q240293/) but how do I create that instance
for the attachment to occur. My application was coded using Visual C++ so
the deployment using the VB Package and Deployment Wizard does not apply. I
looked endless on the web on how to do this but to no avail.
I'm using Installshield X to package my install. I have it setup so that the
MSDE install folder is copied onto the c: drive. But I need to create the
instance in the command line using setup.exe. I don't know how to call the
command line within the Installshield script to create my instance. Am I
headed in the wrong direction or is there some easier way? Any help would be
much appreciated!Hi
These may help!
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/sql_embeddingmsde.asp
http://www.microsoft.com/sql/msde/techinfo/MSDEintegration.asp
John
"luv2travel" wrote:
> Hi there,
> I am having a hard time trying finding information on how to deploy my
> instance along with my application. I found the following link to be useful
> in attaching my database to the server
> (http://support.microsoft.com/kb/q240293/) but how do I create that instance
> for the attachment to occur. My application was coded using Visual C++ so
> the deployment using the VB Package and Deployment Wizard does not apply. I
> looked endless on the web on how to do this but to no avail.
> I'm using Installshield X to package my install. I have it setup so that the
> MSDE install folder is copied onto the c: drive. But I need to create the
> instance in the command line using setup.exe. I don't know how to call the
> command line within the Installshield script to create my instance. Am I
> headed in the wrong direction or is there some easier way? Any help would be
> much appreciated!|||Thanks John!
"John Bell" wrote:
> Hi
> These may help!
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/sql_embeddingmsde.asp
> http://www.microsoft.com/sql/msde/techinfo/MSDEintegration.asp
> John
> "luv2travel" wrote:
> > Hi there,
> >
> > I am having a hard time trying finding information on how to deploy my
> > instance along with my application. I found the following link to be useful
> > in attaching my database to the server
> > (http://support.microsoft.com/kb/q240293/) but how do I create that instance
> > for the attachment to occur. My application was coded using Visual C++ so
> > the deployment using the VB Package and Deployment Wizard does not apply. I
> > looked endless on the web on how to do this but to no avail.
> >
> > I'm using Installshield X to package my install. I have it setup so that the
> > MSDE install folder is copied onto the c: drive. But I need to create the
> > instance in the command line using setup.exe. I don't know how to call the
> > command line within the Installshield script to create my instance. Am I
> > headed in the wrong direction or is there some easier way? Any help would be
> > much appreciated!

deploying MSDE - what do I need to do

We're about to ship a product, and we've used access to develop it to make things easier, but we want to use MSDE.

I've never had any luck with MSDE -

1. I can import the database into a sql server database in enterprise manager, is there a way to import a database into a msde database in interprise manager?

2. what would I do in the installer? I need to install the msde engine right? and then run sql scripts on the engine?

Thanks in advance!Have you read this article...

http://www.msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmsde/html/msdedepl.asp|||thanks! thats exactly what I needed :)

Deploying MSDE

I am writing an application in VB.Net that includes a database. I could use
either an Access database (MS Jet) or MSDE. I would rather use MSDE because
it has useful features like triggers and complex stored procedures, but I am
worried about deployment.
My users have all kinds of machines, running anything from Windows 98 to
Windows Server 2003. Some may already have MSDE or SQL Server 2000 installed,
most will not. I will use Installshield Express 4 to make the deployment
package. Some users will download the package from my web site, some will
receive CDs.
I am worried that the complexities of deploying to such a wide range of
target machines may be too great and that I should revert to using a Jet
database.
Does anybody have relevant experience? Are there any useful books or
articles that I could read?
Many thanks
Peter
I have been thru a similar situation where I had a VB.NET Apps with MSDE and
Installshield for deployment on all win OS. I dont have any books or articles
for the same but I could do that. Installing MSDE on a m/c where it already
has a MSDE or SQL svr is not an issue as u should install MSDE with a new
unique instancename always.
siaj
"PeterH" wrote:

> I am writing an application in VB.Net that includes a database. I could use
> either an Access database (MS Jet) or MSDE. I would rather use MSDE because
> it has useful features like triggers and complex stored procedures, but I am
> worried about deployment.
> My users have all kinds of machines, running anything from Windows 98 to
> Windows Server 2003. Some may already have MSDE or SQL Server 2000 installed,
> most will not. I will use Installshield Express 4 to make the deployment
> package. Some users will download the package from my web site, some will
> receive CDs.
> I am worried that the complexities of deploying to such a wide range of
> target machines may be too great and that I should revert to using a Jet
> database.
> Does anybody have relevant experience? Are there any useful books or
> articles that I could read?
> Many thanks
> --
> Peter

Deploying MSDE

Hi All,
Is it possible to use SQL Server 2000 Developer Edition for development and then deploy the database on MSDE?
Regards.
Yes, it is.
There is very little missing from MSDE, but it has limitations in database
size and number of connections. (Also, see SQL Server 2005 Express Edition
for where this is going.)
Russell Fields
"sm" <sm@.discussions.microsoft.com> wrote in message
news:806DD4DC-6E84-4335-A335-A8DE1E931A8F@.microsoft.com...
> Hi All,
> Is it possible to use SQL Server 2000 Developer Edition for development
and then deploy the database on MSDE?
> Regards.
|||So does all this mean, a VS.NET 2005 developer can create a database in SQL
Server and then ship this free version of SQL Server and it will install
easily.
If so, Hallelujah!
MSDE is a pain to install and especially to have your users install it.
SQL Server is great for large companies but for small scale 5-10 users,
buying a $5000+ product just for a database and having all the management
overhead is a pain in the rear and that is the nitch that jet files have
filled before and MSDE was trying to fill.
For me I want to use a free limited version of SQL Server for such
applications and if the company gets real large and starts needing more then
they can buy the big brother. But I really need it to install easily
without much user intervention.
Is this what we can expect?
Thanks Russell,
Shane
"Russell Fields" <RussellFields@.NoMailPlease.Com> wrote in message
news:OBmBI%23AdEHA.3664@.TK2MSFTNGP12.phx.gbl...
> Yes, it is.
> There is very little missing from MSDE, but it has limitations in database
> size and number of connections. (Also, see SQL Server 2005 Express
Edition
> for where this is going.)
> Russell Fields
> "sm" <sm@.discussions.microsoft.com> wrote in message
> news:806DD4DC-6E84-4335-A335-A8DE1E931A8F@.microsoft.com...
> and then deploy the database on MSDE?
>

Deploying a Database

Hi,
I am creating an application that will use msde, and I would like to know
how to create a sql server in the server application in a straight forward
way to the final user?
any tutorials are appreciated
Thanks in advance
hi Diogo,
Diogo Alves - Software Developer wrote:
> Hi,
> I am creating an application that will use msde, and I would like to
> know how to create a sql server in the server application in a
> straight forward way to the final user?
>
as regard the engine distribution, you can perhaps have a look at
http://www.microsoft.com/downloads/d...displaylang=en ,
a toolkit by Microsoft I'm not confortable with, as I usually use a
companion home built application that provides a visual interface to the
standard MSDE setup.exe boostrap installer, where all desired parameters can
be visually edited by the end user, then "shelling" to the actual installer
providing all parameters...
as regard database deployment, you can have a look at
http://msdn.microsoft.com/msdnmag/is...aseinstaller/, the
best article I know about that stuff, supporting versioning, updates and the
like..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Deploy MSDE using Command

I am using VB6 to install MSDE and here is my syntax.
Setup.exe INSTANCENAME=NK SECURITYMODE=SQL SAPWD=NKM
It will install and show the progress bar all they way to about 4 second
left then freezes up. The log shows this as the last thing it did prior to
locking up "Executing "C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\sqlredis.exe /q:a"
Any idea what went wrong?
hi Grant,
Grant wrote:
> I am using VB6 to install MSDE and here is my syntax.
>
> Setup.exe INSTANCENAME=NK SECURITYMODE=SQL SAPWD=NKM
> It will install and show the progress bar all they way to about 4
> second left then freezes up. The log shows this as the last thing it
> did prior to locking up "Executing "C:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\sqlredis.exe /q:a"
> Any idea what went wrong?
please have a look at http://tinyurl.com/dm5hs
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.16.0 - DbaMgr ver 0.61.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Interesting but I cannot do it through that process. It will be install on
thousands of customer so you can image the volume of calls we will get. I
will look for a different way to deploy MSDE. Thanks.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3vloskF164dfqU1@.individual.net...
> hi Grant,
> Grant wrote:
> please have a look at http://tinyurl.com/dm5hs
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.16.0 - DbaMgr ver 0.61.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>

Deploy database develop from MSDE

Hi,
I have a small access database develop using msde as back end. I want to put
this backend database on shared drive so that other user can access to it.
My question is
1 - Does I need to setup MSDE on every workstation?
2 - Can other user connect to this database using ODBC?
SF
Thank you very much for this useful tip.
SF
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:4s0fftFsu16iU1@.mid.individual.net...
> hi,
> SF wrote:
> SQL Server/MSDE is not a file based database like Access is... so you only
> have to put the database on the machine hosting the MSDE instance (and not
> on a shared folder).. obviously every machine in the lan can then access
> the MSDE service...
> ODBC api? yes, if you like the hard way, but you probably shoud consider
> other data acces methods, like ADO, Ado.Net and the like...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
> -- remove DMO to reply
>

Deny remote network access to MSDE

HI!
I'd like turn off remote network access for a user group in the user
manager.
Are users of this group still capable of accessing the MSDE while
working on the local machine?
What does local access mean?
Can they access the MSDE via TCP to 127.0.0.1?
Or must they access the MSDE through a named pipe?
Ciao, Michael.
If I'm not mistaken, MSDE 2000 SP3a already disables remote access by
default.
joe.
"Michael Strder" <michael@.stroeder.com> wrote in message
news:sauhi2-5k4.ln1@.nb2.stroeder.com...
> HI!
> I'd like turn off remote network access for a user group in the user
> manager.
> Are users of this group still capable of accessing the MSDE while
> working on the local machine?
> What does local access mean?
> Can they access the MSDE via TCP to 127.0.0.1?
> Or must they access the MSDE through a named pipe?
> Ciao, Michael.

Deny remote access to MSDE for some users

HI!
I'm a complete MSDE newbie but I have to clarify an open question about
access control with MSDE 2000 running on WinNT 4.0:
Is it possible to grant some admin users remote access to the MSDE but
restrict other local users to local access?
Ciao, Michael.
hi Michael,
Michael Strder wrote:
> HI!
> I'm a complete MSDE newbie but I have to clarify an open question
> about access control with MSDE 2000 running on WinNT 4.0:
> Is it possible to grant some admin users remote access to the MSDE but
> restrict other local users to local access?
yes, of course..
you have to grant the remote logins access to the MSDE instance via the
sp_grantlogin system stored procedure
(http://msdn.microsoft.com/library/de...-us/tsqlref/ts
_sp_ga-gz_8dri.asp), while you have to deny local logins via sp_denylogin...
please have a look at
http://support.microsoft.com/default...;EN-US;q325003 for futher
info about how to perform these tasks via oSql.exe, the command line tool
provided with MSDE
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Andrea,
first many thanks for the pointers.
Andrea Montanari wrote:
> hi Michael,
> Michael Strder wrote:
> you have to grant the remote logins access to the MSDE instance via the
> sp_grantlogin system stored procedure
> (http://msdn.microsoft.com/library/de...-us/tsqlref/ts
> _sp_ga-gz_8dri.asp), while you have to deny local logins via sp_denylogin...
Let's assume I use Windows authentication for MSDE. Is the whole access
control also done via Windows rights based on groups? How to disallow a
remote login for local users then?
Ciao, Michael.
|||ciao Michael,
> ..
> Let's assume I use Windows authentication for MSDE. Is the whole
> access control also done via Windows rights based on groups? How to
> disallow a remote login for local users then?
let's say you have YourDomain\theUser member of TheGroup\
you want TheGroup\ to be able to connect to MSDE, so you grant
(sp_grantlogin) it connection...
but you want YourDomain\theUser not to be able to connect to MSDE .. you
deny YourDomain\theUser connection to MSDE via sp_denylogin...
this way you have YourDomain\TheGroup able to connect and YourDomain\theUser
unable...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply