Creation of Instance.

I have been doing research on how to create a new instance with MSDE. Does anyone know how to create one in an automated fashion using one of the standard tools that are installed with MSDE 2000A? I suspect that is accomplished with cnfgsvr.exe but have
not found any examples on the Internet. Thanks.
Message posted via http://www.sqlmonster.com
hi Thomas,
Thomas Vollmer via SQLMonster.com wrote:
> I have been doing research on how to create a new instance with MSDE.
> Does anyone know how to create one in an automated fashion using one
> of the standard tools that are installed with MSDE 2000A? I suspect
> that is accomplished with cnfgsvr.exe but have not found any examples
> on the Internet. Thanks.
in order to install a brand new MSDE instalnce you only have to run it's
setup.exe bootstrapp installer ..
MSDE does not provide support for response files nor for for unattended
installations...
http://msdn.microsoft.com/library/de...stsql_84xl.asp
regards
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

Creating/Running DTS Packages with MSDE

Hi,
Is it possible to create DTS packages with MSDE? If so, how?
Would you execute them via the "dtsrun" command-prompt utility?
Thanks very much,
Mark Holahan
MSDE does not come with the tools that are necessary to create DTS packages.
For that you will need to user Enterprise Manager, which come with the full
versions of SQL Server, including the Developers version. MSDE instances can
store DTS packages in their repository and MSDE 2000 comes with the
dtsrun.exe utility, allowing you to execute packages.
Jim
"Mark Holahan" <mark.holahan@.unifiedllc.com> wrote in message
news:e93IFVWBFHA.3504@.TK2MSFTNGP12.phx.gbl...
> Hi,
> Is it possible to create DTS packages with MSDE? If so, how?
> Would you execute them via the "dtsrun" command-prompt utility?
> Thanks very much,
> Mark Holahan
>

Creating user

Hi,
I've just installed MSDE, and I'm wondering how to create user so I
don't have to login as 'sa' user.
Thanks in advance
ukasz
Try:
sp_addlogin '<userName','<password>'
Look for sp_addlogin / sp_grantlogin in the BOL.
HTH, Jens Suessmeyer.
|||Hi,
To add on Jens:-
MSDE will not come with GUI tools; so you need to login using OSQL to sql
server and issue TSQL commands to create Logins and users.
For eg; if you need to create a user HARI with read only rights in Finance
database then:-
From command line:-
OSQL -S <servername> -Usa -P<sapassword> (enter)
SP_addlogin 'hari','haripass'
go <enter>
Use Finance
go <enter>
sp_adduser 'hari'
go <enter>
sp_addrolemember 'db_datareader','hari'
go <enter>
he above commands will create user Hari with read rights in Finance
database.
Thanks
Hari
SQL Server MVP
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1126692828.991504.289480@.g47g2000cwa.googlegr oups.com...
> Try:
> sp_addlogin '<userName','<password>'
> Look for sp_addlogin / sp_grantlogin in the BOL.
> HTH, Jens Suessmeyer.
>
|||Hari Prasad wrote:
> Hi,
> To add on Jens:-
> MSDE will not come with GUI tools; so you need to login using OSQL to sql
> server and issue TSQL commands to create Logins and users.
> For eg; if you need to create a user HARI with read only rights in Finance
> database then:-
> From command line:-
> OSQL -S <servername> -Usa -P<sapassword> (enter)
> SP_addlogin 'hari','haripass'
> go <enter>
> Use Finance
> go <enter>
> sp_adduser 'hari'
> go <enter>
> sp_addrolemember 'db_datareader','hari'
> go <enter>
> he above commands will create user Hari with read rights in Finance
> database.
> Thanks
> Hari
> SQL Server MVP
>
>
> "Jens" <Jens@.sqlserver2005.de> wrote in message
> news:1126692828.991504.289480@.g47g2000cwa.googlegr oups.com...
>
>
Thanks.
|||Hari Prasad wrote:
> Hi,
> To add on Jens:-
> MSDE will not come with GUI tools; so you need to login using OSQL to sql
> server and issue TSQL commands to create Logins and users.
> For eg; if you need to create a user HARI with read only rights in Finance
> database then:-
> From command line:-
> OSQL -S <servername> -Usa -P<sapassword> (enter)
> SP_addlogin 'hari','haripass'
> go <enter>
> Use Finance
> go <enter>
> sp_adduser 'hari'
> go <enter>
> sp_addrolemember 'db_datareader','hari'
> go <enter>
> he above commands will create user Hari with read rights in Finance
> database.
> Thanks
> Hari
> SQL Server MVP
>
>
> "Jens" <Jens@.sqlserver2005.de> wrote in message
> news:1126692828.991504.289480@.g47g2000cwa.googlegr oups.com...
>
>
Thanks
ukasz

creating stored procedures with msde ?

hye
Do ny help me by telling
1. Can we create stored procedures with MSDE ?
2. How can we include stored procedures with deployment ?
3. How can we install MSDE with our application ?
Vijay,
1. Yes
2. You install stored procedures with a SQL script
3. Check out
http://msdn.microsoft.com/library/de...l/msdedepl.asp
Jon Jahren
"vijay" <vkodwani@.ce.com.pk> wrote in message
news:8d5a15e3.0411110415.69d6ab90@.posting.google.c om...
> hye
> Do ny help me by telling
> 1. Can we create stored procedures with MSDE ?
> 2. How can we include stored procedures with deployment ?
> 3. How can we install MSDE with our application ?

Creating SQL Server Databases With No Security Restrictions

First, let me apologize for crossposting and the lengthy post, but this
question involved both MSDE and (I believe) security settings.
We use Visual Studio .NET 2003 with MSDE in classrooms and labs and have
had no security issues once things were configured properly for student
access. The sample databases install and work correctly for any authorized
users who might be logged on to a given PC.
We are using a text that supplies .mdf files as part of the support
materials for the book. We are able to copy the .mdf files to the
appropriate directory (..\Microsoft SQL Server\MSSQL$InstanceName\Data),
then use Server Explorer in VS .NET to create a database link to the file
(Connect To Database button on the Server Explorer toolbar). Once VS .NET is
restarted, the database appears in the list of databases under the SQL
Server instance and is fully accessible.
I now want to create additional SQL Server databases for students to use
with development projects, etc. I have access to the SQL Server GUI
management tools (from our MSDNAA subscription) and they are installed and
working with the MSDE instance on my office PC. When I create a
database/tables/etc. on my instance, then attempt to copy the .mdf to
another PC to use the setup technique described above, a window pops up
wanting me to select a security option and then refuses me access to the new
database regardless of the option (NT Security or database
username/password) I try to choose.
After all that, what I'm seeking is the way to create a database to export
to any PC, with any student or faculty member logged on so that they can
import the .mdf file and connect to it using Server Explorer *without*
encountering security issues. So, when I'm creating a database, what
settings do I apply so that it doesn't care who is interacting with it?
Thanks in advance for reading and any insights!
hi Peter,
Peter van der Goes wrote:
> First, let me apologize for crossposting and the lengthy post, but
> this question involved both MSDE and (I believe) security settings.
> We use Visual Studio .NET 2003 with MSDE in classrooms and labs and
> have had no security issues once things were configured properly for
> student access. The sample databases install and work correctly for
> any authorized users who might be logged on to a given PC.
> We are using a text that supplies .mdf files as part of the support
> materials for the book. We are able to copy the .mdf files to the
> appropriate directory (..\Microsoft SQL
> Server\MSSQL$InstanceName\Data), then use Server Explorer in VS .NET
> to create a database link to the file (Connect To Database button on
> the Server Explorer toolbar). Once VS .NET is restarted, the database
> appears in the list of databases under the SQL Server instance and is
> fully accessible.
> I now want to create additional SQL Server databases for students to
> use with development projects, etc. I have access to the SQL Server
> GUI management tools (from our MSDNAA subscription) and they are
> installed and working with the MSDE instance on my office PC. When I
> create a database/tables/etc. on my instance, then attempt to copy
> the .mdf to another PC to use the setup technique described above, a
> window pops up wanting me to select a security option and then
> refuses me access to the new database regardless of the option (NT
> Security or database username/password) I try to choose.
> After all that, what I'm seeking is the way to create a database to
> export to any PC, with any student or faculty member logged on so
> that they can import the .mdf file and connect to it using Server
> Explorer *without* encountering security issues. So, when I'm
> creating a database, what settings do I apply so that it doesn't care
> who is interacting with it?
> Thanks in advance for reading and any insights!
in order to attach an existing db file, as long as create a brand new
database, the logged user must be member of the sysadmin and/or dbcreator
server role...
in order to connect to an MSDE instance you have to provide a login
information, both for Windows NT (trusted) authenticated or SQL Server
authenticated connections, as you provide this kind of information in the
Data Link dialog to (Connect To Database button on the Server Explorer
toolbar)... so there's no difference in the behaviour you are
experimenting..
what kind of error do you get when accessing the attached database?
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
|||"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:36sc8vF556sgkU1@.individual.net...
> hi Peter,
> in order to attach an existing db file, as long as create a brand new
> database, the logged user must be member of the sysadmin and/or dbcreator
> server role...
> in order to connect to an MSDE instance you have to provide a login
> information, both for Windows NT (trusted) authenticated or SQL Server
> authenticated connections, as you provide this kind of information in the
> Data Link dialog to (Connect To Database button on the Server Explorer
> toolbar)... so there's no difference in the behaviour you are
> experimenting..
> what kind of error do you get when accessing the attached database?
> --
> 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
>
Thanks for responding, Andrea.
The issue is not permissions assigned to a given user (all users must log on
to any campus PC, thus providing username/password information), but the
difference between a .mdf file I create vs. those supplied by the publisher
of the textbook.
When we work with the .mdf files supplied by the publisher, there is no
issue with requested authentication information. Any user who can log onto a
campus PC can copy the .mdf file to the correct location on that PC, follow
the procedures I outlined in my original post using Visual Studio .NET 2003
Server Explorer and "create" an accessible database using the file in
question, then access it and its objects in Server Explorer at will. Some
setting in that .mdf file is allowing this behavior for any user. This
database can be "opened" by anybody who logs onto that PC and uses Server
Explorer.
When I create a database (.mdf) file using SQL Server Enterprise Manager and
try to "create" a database from it on a different PC, the process appears to
work. When I subsequently attempt to open that database in Server Explorer
(by clicking on the + next to the newly-created database name), I get a
dialog box insisting that I supply either NT Security information or, select
SQL Server access and provide a username/password for the database. Any
combination of username/password information I supply at that stage is
rejected by the dialog. When I open a database supplied by the publisher, no
such dialog appears and I have full access. My goal is to create databases
which behave like those supplied by the publisher.
As the security issue does not occur when using the .mdf files provided by
the publisher, I can only assume that these files were from databases set up
as accessible to all. As I'm not smart on SQL Server administration
(everything I "know" comes from SQL Server 2000 Programming, Step by Step
from MS Press), I'm hoping that somebody will guide me to the correct
settings for a SQL Server database so it's openly accessible to any user who
logs onto a PC where the database resides without triggering any
authentication dialogs. For what it's worth, I can replicate all the
behaviors above on my home PC which just uses a simple default logon.
I can send you (or, anybody else) one of the publisher's .mdf files if it
would help identify the settings in question.
|||On Tue, 8 Feb 2005 12:50:40 -0600, Peter van der Goes wrote:

> When I create a database (.mdf) file using SQL Server Enterprise Manager and
> try to "create" a database from it on a different PC, the process appears to
> work. When I subsequently attempt to open that database in Server Explorer
> (by clicking on the + next to the newly-created database name), I get a
> dialog box insisting that I supply either NT Security information or, select
> SQL Server access and provide a username/password for the database. Any
> combination of username/password information I supply at that stage is
> rejected by the dialog. When I open a database supplied by the publisher, no
> such dialog appears and I have full access. My goal is to create databases
> which behave like those supplied by the publisher.
Perhaps this would do the trick:
EXECUTE sp_grantdbaccess guest
EXECUTE sp_addrolemember 'db_owner',guest
Sorry, but I couldn't find an equivalent to this in Enterprise Manager, so
execute it from Query Analyzer.
|||"Ross Presser" <rpresser@.imtek.com> wrote in message
news:uauu8880rpzp$.dlg@.rpresser.invalid...
> On Tue, 8 Feb 2005 12:50:40 -0600, Peter van der Goes wrote:
> Perhaps this would do the trick:
> EXECUTE sp_grantdbaccess guest
> EXECUTE sp_addrolemember 'db_owner',guest
> Sorry, but I couldn't find an equivalent to this in Enterprise Manager, so
> execute it from Query Analyzer.
Unfortunately, the commands didn't alter the situation. However, through
additional experimentation, I've discovered the following:
The database itself is OK, as I can access it in Enterprise Manager. In
Server Explorer, the database appears, but its State property says
"Disconnected" and I get the SQL Server authentication dialog when Server
Explorer attempts to connect. I've checked the database file's network
security properties, and they appear to be set the same as those for the
database files (from the book) that I am able to access in Server Explorer.
Public has full access. I'm beginning to think I'm dealing with a NTFS file
or folder access issue, as the same database is fully accessible through
Server Explorer on a PC with a FAT32 partition?!?

Creating SQL Server Databases With No Security Restrictions

First, let me apologize for crossposting and the lengthy post, but this
question involved both MSDE and (I believe) security settings.
We use Visual Studio .NET 2003 with MSDE in classrooms and labs and have
had no security issues once things were configured properly for student
access. The sample databases install and work correctly for any authorized
users who might be logged on to a given PC.
We are using a text that supplies .mdf files as part of the support
materials for the book. We are able to copy the .mdf files to the
appropriate directory (..\Microsoft SQL Server\MSSQL$InstanceName\Data),
then use Server Explorer in VS .NET to create a database link to the file
(Connect To Database button on the Server Explorer toolbar). Once VS .NET is
restarted, the database appears in the list of databases under the SQL
Server instance and is fully accessible.
I now want to create additional SQL Server databases for students to use
with development projects, etc. I have access to the SQL Server GUI
management tools (from our MSDNAA subscription) and they are installed and
working with the MSDE instance on my office PC. When I create a
database/tables/etc. on my instance, then attempt to copy the .mdf to
another PC to use the setup technique described above, a window pops up
wanting me to select a security option and then refuses me access to the new
database regardless of the option (NT Security or database
username/password) I try to choose.
After all that, what I'm seeking is the way to create a database to export
to any PC, with any student or faculty member logged on so that they can
import the .mdf file and connect to it using Server Explorer *without*
encountering security issues. So, when I'm creating a database, what
settings do I apply so that it doesn't care who is interacting with it?
Thanks in advance for reading and any insights!hi Peter,
Peter van der Goes wrote:
> First, let me apologize for crossposting and the lengthy post, but
> this question involved both MSDE and (I believe) security settings.
> We use Visual Studio .NET 2003 with MSDE in classrooms and labs and
> have had no security issues once things were configured properly for
> student access. The sample databases install and work correctly for
> any authorized users who might be logged on to a given PC.
> We are using a text that supplies .mdf files as part of the support
> materials for the book. We are able to copy the .mdf files to the
> appropriate directory (..\Microsoft SQL
> Server\MSSQL$InstanceName\Data), then use Server Explorer in VS .NET
> to create a database link to the file (Connect To Database button on
> the Server Explorer toolbar). Once VS .NET is restarted, the database
> appears in the list of databases under the SQL Server instance and is
> fully accessible.
> I now want to create additional SQL Server databases for students to
> use with development projects, etc. I have access to the SQL Server
> GUI management tools (from our MSDNAA subscription) and they are
> installed and working with the MSDE instance on my office PC. When I
> create a database/tables/etc. on my instance, then attempt to copy
> the .mdf to another PC to use the setup technique described above, a
> window pops up wanting me to select a security option and then
> refuses me access to the new database regardless of the option (NT
> Security or database username/password) I try to choose.
> After all that, what I'm seeking is the way to create a database to
> export to any PC, with any student or faculty member logged on so
> that they can import the .mdf file and connect to it using Server
> Explorer *without* encountering security issues. So, when I'm
> creating a database, what settings do I apply so that it doesn't care
> who is interacting with it?
> Thanks in advance for reading and any insights!
in order to attach an existing db file, as long as create a brand new
database, the logged user must be member of the sysadmin and/or dbcreator
server role...
in order to connect to an MSDE instance you have to provide a login
information, both for Windows NT (trusted) authenticated or SQL Server
authenticated connections, as you provide this kind of information in the
Data Link dialog to (Connect To Database button on the Server Explorer
toolbar)... so there's no difference in the behaviour you are
experimenting..
what kind of error do you get when accessing the attached database?
--
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|||"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:36sc8vF556sgkU1@.individual.net...
> hi Peter,
> in order to attach an existing db file, as long as create a brand new
> database, the logged user must be member of the sysadmin and/or dbcreator
> server role...
> in order to connect to an MSDE instance you have to provide a login
> information, both for Windows NT (trusted) authenticated or SQL Server
> authenticated connections, as you provide this kind of information in the
> Data Link dialog to (Connect To Database button on the Server Explorer
> toolbar)... so there's no difference in the behaviour you are
> experimenting..
> what kind of error do you get when accessing the attached database?
> --
> 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
>
Thanks for responding, Andrea.
The issue is not permissions assigned to a given user (all users must log on
to any campus PC, thus providing username/password information), but the
difference between a .mdf file I create vs. those supplied by the publisher
of the textbook.
When we work with the .mdf files supplied by the publisher, there is no
issue with requested authentication information. Any user who can log onto a
campus PC can copy the .mdf file to the correct location on that PC, follow
the procedures I outlined in my original post using Visual Studio .NET 2003
Server Explorer and "create" an accessible database using the file in
question, then access it and its objects in Server Explorer at will. Some
setting in that .mdf file is allowing this behavior for any user. This
database can be "opened" by anybody who logs onto that PC and uses Server
Explorer.
When I create a database (.mdf) file using SQL Server Enterprise Manager and
try to "create" a database from it on a different PC, the process appears to
work. When I subsequently attempt to open that database in Server Explorer
(by clicking on the + next to the newly-created database name), I get a
dialog box insisting that I supply either NT Security information or, select
SQL Server access and provide a username/password for the database. Any
combination of username/password information I supply at that stage is
rejected by the dialog. When I open a database supplied by the publisher, no
such dialog appears and I have full access. My goal is to create databases
which behave like those supplied by the publisher.
As the security issue does not occur when using the .mdf files provided by
the publisher, I can only assume that these files were from databases set up
as accessible to all. As I'm not smart on SQL Server administration
(everything I "know" comes from SQL Server 2000 Programming, Step by Step
from MS Press), I'm hoping that somebody will guide me to the correct
settings for a SQL Server database so it's openly accessible to any user who
logs onto a PC where the database resides without triggering any
authentication dialogs. For what it's worth, I can replicate all the
behaviors above on my home PC which just uses a simple default logon.
I can send you (or, anybody else) one of the publisher's .mdf files if it
would help identify the settings in question.|||On Tue, 8 Feb 2005 12:50:40 -0600, Peter van der Goes wrote:

> When I create a database (.mdf) file using SQL Server Enterprise Manager a
nd
> try to "create" a database from it on a different PC, the process appears
to
> work. When I subsequently attempt to open that database in Server Explorer
> (by clicking on the + next to the newly-created database name), I get a
> dialog box insisting that I supply either NT Security information or, sele
ct
> SQL Server access and provide a username/password for the database. Any
> combination of username/password information I supply at that stage is
> rejected by the dialog. When I open a database supplied by the publisher,
no
> such dialog appears and I have full access. My goal is to create databases
> which behave like those supplied by the publisher.
Perhaps this would do the trick:
EXECUTE sp_grantdbaccess guest
EXECUTE sp_addrolemember 'db_owner',guest
Sorry, but I couldn't find an equivalent to this in Enterprise Manager, so
execute it from Query Analyzer.|||"Ross Presser" <rpresser@.imtek.com> wrote in message
news:uauu8880rpzp$.dlg@.rpresser.invalid...
> On Tue, 8 Feb 2005 12:50:40 -0600, Peter van der Goes wrote:
> Perhaps this would do the trick:
> EXECUTE sp_grantdbaccess guest
> EXECUTE sp_addrolemember 'db_owner',guest
> Sorry, but I couldn't find an equivalent to this in Enterprise Manager, so
> execute it from Query Analyzer.
Unfortunately, the commands didn't alter the situation. However, through
additional experimentation, I've discovered the following:
The database itself is OK, as I can access it in Enterprise Manager. In
Server Explorer, the database appears, but its State property says
"Disconnected" and I get the SQL Server authentication dialog when Server
Explorer attempts to connect. I've checked the database file's network
security properties, and they appear to be set the same as those for the
database files (from the book) that I am able to access in Server Explorer.
Public has full access. I'm beginning to think I'm dealing with a NTFS file
or folder access issue, as the same database is fully accessible through
Server Explorer on a PC with a FAT32 partition?!?

Creating relationships with MSDE

Is it possible to create relationships between tables using foregin keys with MSDE. I have looked for any information and can't seem to find anything.With MSDE you can use Visual Studio and MS Access. With Access you have to create new Data Project. Also you can use SQL Server Enterprise Manager to create relationships. But, you can be always more elite and use oSQL and create relations using SQL.

If you prefer writing SQL for relations then you should read T-SQL documentation. Check out chapters for CREATE TABLE and ALTER TABLE statements.|||Yes. You can create realationships as mentioned. Is there specific information you would like to know.|||Thanks Guys.

Helps to know that I wasn't going to crazy trying to figure it out.

Creating new users with MSDE

I have MSDE installed on my sistem, and I need to add a new user.
How do I go about doing this?Hi,

MSDE do not have user interface thus all manipulation can be done
using SQL-DMO and Visual Basic (Assume you are using VB6.0).

Add reference to "Microsoft SQL-DMO object librarary", in that you can
use login class to add login. In fact you can completely manage and
operate SQL Server/MSDE using SQL-DMO.

Hope this helps you.

Thanks, Amit

thirdmarshaleomer@.hotmail.com (Kyle) wrote in message news:<2d9cd550.0306271223.27e14f57@.posting.google.com>...
> I have MSDE installed on my sistem, and I need to add a new user.
> How do I go about doing this?|||if you have 19$ take a look at www.msde.biz

hth,
Helmut

"Kyle" <thirdmarshaleomer@.hotmail.com> schrieb im Newsbeitrag
news:2d9cd550.0306271223.27e14f57@.posting.google.c om...
> I have MSDE installed on my sistem, and I need to add a new user.
> How do I go about doing this?

Creating multiple databases running off the same Data Engine

Hi, I have looked and loked for the answer to this question and made no progress.
I want to install MSDE on one of our servers, however, when I went to install it, I found that there was another MSDE already installed and running (it was an agent running with our backup software Veritas). Is it alright to create another database and have 2 running simultaneous on the same data engine? Is there any type of limitations that I sould know about - such as number of allowed accesses at one time? Any help is greatly appreicated.You can create another database with the existing MSDE but if you are on a large network I would install another instance and get the Developer edition to manage them that way you will avoid the risk of running your application on MSDE that is already used to the max in system resources. I have seen SQL Server running without databases because it is used to run xp_cmdshell to move data from DB2 AS400 to live SQL Server on the web about four hours a day. Try the link below to buy the Developer edition. When you have installed the Developer edition you right click at the top of Enterprise manager and register both. Hope this helps.
http://www.provantage.com/buy-22053391-microsoft-backoffice-sql-server-2000-developer-edition-shopping.htm

Creating maintenance plans in MSDE

I can create a maintenance plan in Enterprisemanager using the maintenance plan wizard. It automatically creates 4 different jobs. I can generate a script for those jobs and run using a batch file in MSDE. Is there another way to do the same thing. How c
an i create maintenance plans in MSDE
Hi,
You need to just run the same types of scripts against the MSDE. Use OSQL or
a 3rd party tool.
HTH,
Greg Low (MVP)
MSDE Manager SQL Tools
www.whitebearconsulting.com
"hp" <anonymous@.discussions.microsoft.com> wrote in message
news:E4C10AAD-2B43-4BDE-B1B1-C23D326CAE19@.microsoft.com...
> I can create a maintenance plan in Enterprisemanager using the maintenance
plan wizard. It automatically creates 4 different jobs. I can generate a
script for those jobs and run using a batch file in MSDE. Is there another
way to do the same thing. How can i create maintenance plans in MSDE
|||These articles may help you get started:
241397 HOWTO: Back Up a Microsoft Data Engine Database with Transact-SQL
http://support.microsoft.com/?id=241397
328747 INF: Recovery Planning for Microsoft SQL Server 2000 Desktop Engine
http://support.microsoft.com/?id=328747
325003 HOW TO: Manage the SQL Server Desktop Engine (MSDE 2000) by Using the
http://support.microsoft.com/?id=325003
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Creating Log file & Attaching db?

Bit of a SQL newbie, having taken over a support role for a piece of software that my firm sells. It is basically a DB that runs on MSDE or SQL Server in either desktop or enterprise scenarios.

We do sell our software to clients who may or may not already have SQL on their machines. During installation, it searches for sqlservr.exe for existing SQL installations and if it finds nothing, will then install MSDE 1.0 to house the db files.

My question is this -

I can manually create a db or manually attach an existing db through sql query analyser where there is a full-blown SQL installation. Is there any way I can do the same where there is only MSDE installed? The simple solution, I guess, would be to download one of the freeware or shareware MSDE "Enterprise Managers", but this won't always be suitable for a client installation.

Many thanks for your assistance all.

:cool:you could use sp_attach_db to attach a sqlserver database to sqlserver. Don't know about msde though.|||you could use sp_attach_db to attach a sqlserver database to sqlserver. Don't know about msde though.

Thanks

Yep, this is what I would use if I was doing it through the SQL. Still wondering about MSDE tho.
:confused:|||You can look into SQL-DMO and write up a quick routine that would do the attaching.

Creating Job to do Daily Backup

I have a client that is using the free MSDE database engine. There is no graphical interface that I know of to manage the day-to-day tasks. I need to do a daily backup to a disk file. I want to start the backup at 7:40pm. My client then will copy that disk file to tape duing his system-wide backup at midnight. I setup a batch file and executed it in osql but the job is not working. No disk file has been created in the last 3 weeks. I don't have a clue what I am missing. Can someone please look at this and tell me how to fix it?

Thanks in Advance!

Debbie Erickson

USE master
EXEC msdb..sp_delete_jobserver
@.job_name='PetDB Backup',
@.server_name='Server06'
GO

USE master
EXEC msdb..sp_delete_jobschedule
@.job_name='PetDB Backup',
@.name = 'ScheduledBackup'
GO

USE master
EXEC msdb..sp_delete_jobstep
@.job_name='PetDB Backup',
@.step_id=0
GO

USE master
EXEC msdb..sp_delete_job
@.job_name='PetDB Backup'
GO

USE master
EXEC msdb..sp_add_job
@.job_name='PetDB Backup',
@.enabled=1,
@.description='Backup Petdb'
GO

USE master
EXEC msdb..sp_add_jobstep
@.job_name='PetDB Backup',
@.step_name='Nightly petdb maint',
@.subsystem='TSQL',
@.command='BACKUP DATABASE Petdb TO DISK = ''E:Petlic\Data Backup\Petdb.bak''',
@.database_name='petdb'
GO

USE master
EXEC msdb..sp_add_jobschedule
@.job_name='PetDB Backup',
@.name = 'ScheduledBackup',
@.freq_type=4,
@.freq_interval=1,
@.active_start_time='194000'
GO

USE master
EXEC msdb..sp_add_jobserver
@.job_name='PetDB Backup',
@.server_name='Server06'
GO

Does BACKUP DATABASE Petdb TO DISK = ''E:Petlic\Data Backup\Petdb.bak'' (copied exactly from your job) work OK when run via osql?|||

Hello again. I decided to go a slightly different path. The backup statement works fine in osql. So I put that command in a text file by itself. Then I created a dos batch file that runs osql with sql batch file. Then I used a windows scheduler to run my dos batch file. Not exactly how I wanted to solve this, but it works.

Debbie