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 problems - no components for DataFlow

I’ve created a SSIS package that has 2 tasks. The first is selecting some information from a SQL Server table and the second is exporting this information to a flat file.

I created the package on my desktop client and I am able to run it successfully in Debug mode from my client. The information is selected from the LIVE SQL Server database and the file is created on the LIVE SQL Server.

I have built the package for deployment, copied it to the LIVE SQL Server and have run the manifest file to deploy it.

I’ve logged into the SSIS on the LIVE server and the package is listed there. However when I right click on it and run it I get some error messages indicating that the dataflow tasks have no components, presumably the select statement and the export to the flat file.

It’s as if when I build the package the data components are not being included or when I deploy it on the LIVE server the data components are not being deployed.

Does anyone have suggestions?

Could you report the actual error message you are getting? Empty data flows only generate warnings, not errors.|||

The exact error is:

DocumentL Listing

Validation has started.

Export Document Listing

Validation has started

Warning: The DataFlow task has no components. Add components or remove the task

Validation is completed

Validation has started

Warning: The DataFlow task has no components. Add components or remove the task

...

|||

Rob,

I know about this problem only too well. Are you using a source control system?

-Jamie

|||

We are using Visual source Safe, but I do not believe that it is installed on any of the computers discussed here.

Are you saying that this may be a problem with the Source Safe integration with SQL 2005?

|||

Rob Woods wrote:

We are using Visual source Safe, but I do not believe that it is installed on any of the computers discussed here.

Rob Woods wrote:

So that package that we're talking about. Does it ever get stored in SourceSafe?

Are you saying that this may be a problem with the Source Safe integration with SQL 2005?

Not exactly. There's a problem with all source control systems when used in conjunction with the SSIS Designer - I have seen it happen with SourceSafe and TFS. The SSIS team are aware of it and are investigating. Long answer is that the contents of the data-flow doesn't get serialized correctly into the .dtsx file due to some sort of problem when used with a source control system. Short answer is that there is a bug.

I really should blog this

-Jamie

|||So is there a work around?|||

Rob Woods wrote:

So is there a work around?

Best I can offer is that seeing as you are using a source control system you can go back and find the most recent version that still contains all the components, and redo all of your changes. Not great!

-Jamie

|||

Jamie Thomson wrote:

I really should blog this

And now I have done: http://blogs.conchango.com/jamiethomson/archive/2007/04/24/SSIS_3A00_-Bug-when-using-source-control-systems.aspx

-Jamie

Deployment from SQL 2000 to SQL 2005

I will be moving my website from my local dev server to the live environment soon. I've been using SQL 2000 to develop, but the live DB is SQL 2005. My app uses exclusively stored procedures for all data access.

What suprises are in store for me when I migrate the site?!

Thanks, Jamie

If you don't have any DTS, scheduled tasks to worry about. Then the migration is very straight forward, personally, I have not encounter any problems. What I did is to script the entire DB's table def, indexes, sp, udf. Then run it once on 2005.

This article contains step-by-step process:http://www.aspfree.com/c/a/MS-SQL-Server/Moving-Data-from-SQL-Server-2000-to-SQL-Server-2005/

Deployment - Database Configurations

Greetings,

I've been looking around all morning and can't seem to find a good answer on this so I thought I'd post a message here.

I'm using the recommended practice of keeping the ASPNETDB.MDF data separate from my site data. (I have my site data located in separate databases but still keep them in the App_Data directory.)

I'm using SQL Server 2005 Express on a Server 2003 box and I've implemented scheduled backups on the databases in the Sql Server.

The questions I'm having are:

1. Why isn't the ASPNETDB.MDF database getting attached to the server? Is it using User Instances?

2. If it is using User Instance then isn't this degrading performance? If so, how to force it to not use User Instance?

3. If User Instance is how it is supposed to work then how are we supposed to do a full backup of the ASPNETDB.MDF database if it isn't attached in the server? (xcopy doesn't seem to work on User Instances because of the dreaded "is being used by another process" error.)

Any recommendations, advice, links, or answers to my questions would be greatly appreciated.

1. Yes.

2. Yes, but insignificantly.

3. I believe backup software that is designed to do backups of live SQL Databases (using SQL Agents), can backup User Instances. However, if you are using SQL Express, you are likely running a low traffic site, and it might be easier to run a batch process that stops the IIS Application, xcopy the .MDF and restart the application. You can probably write a quick batch file to create a dummy offline.htm file into your web application directory, wait a few seconds, xcopy, then delete offline.htm.

There may be better approaches, but those are the ones I have off the top of my head, and I don't claim to have a vast knowledge of running Express databases on live servers.

Deploying MS03-031 patch on cluster

The only problem I've had with it is documented in
http://support.microsoft.com/?kbid=826161.
Other than that, I'd suggest opening a support case on it. When you open a
support case, make certain the person taking the details knows right up
front that this is a SQL Server cluster issue. That will get you directed
to the appropriate place. If you start getting the finger pointing routine,
ask to speak to the support manager, because that problem isn't supposed to
happen anymore.
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com
What problem are you having with the installation?
Rand
This posting is provided "as is" with no warranties and confers no rights.

Deny login for SQL Server Authenticated accounts

Hi,
I want to prevent users from logging into a database temporarily (once a
weekly for a few hours), and once I've updated the tables in the database, I
need to allow all users access again.
I have looked at the system stored procedure sp_denylogin, but this only
works for NT Authenticated accounts. Is there an equivalent system stored
procedure for denying logins for accounts created with AQL Server
Authentication?
Your help will be greatly appreciated.
In the script that updates this, place at the top:
ALTER DATABASE databasename SET SINGLE_USER WITH ROLLBACK IMMEDIATE
At the end of the script, put:
ALTER DATABASE databasename SET MULTI_USER
"Eric" <Eric@.discussions.microsoft.com> wrote in message
news:EE89773B-5F28-4760-B1AF-8C0347A69DF9@.microsoft.com...
> Hi,
> I want to prevent users from logging into a database temporarily (once a
> weekly for a few hours), and once I've updated the tables in the database,
I
> need to allow all users access again.
> I have looked at the system stored procedure sp_denylogin, but this only
> works for NT Authenticated accounts. Is there an equivalent system stored
> procedure for denying logins for accounts created with AQL Server
> Authentication?
> Your help will be greatly appreciated.
>
|||Hi,
I recommend you to start the database in SINGLE USER mode or set the
database to RESTRICTED mode before changing rhe schema.
ALTER DATABASE <DBNAME> set SINGLE_USER
or
ALTER DATABASE <DBNAME> set RESTRICTED_USER
Once the schema change is over you set back to multi user mode.
ALTER DATABASE <DBNAME> set MULTI_USER
Thanks
Hari
SQL Server MVP
"Eric" <Eric@.discussions.microsoft.com> wrote in message
news:EE89773B-5F28-4760-B1AF-8C0347A69DF9@.microsoft.com...
> Hi,
> I want to prevent users from logging into a database temporarily (once a
> weekly for a few hours), and once I've updated the tables in the database,
> I
> need to allow all users access again.
> I have looked at the system stored procedure sp_denylogin, but this only
> works for NT Authenticated accounts. Is there an equivalent system stored
> procedure for denying logins for accounts created with AQL Server
> Authentication?
> Your help will be greatly appreciated.
>
|||Hi Hari,
Tried running this in the SQL Query Analyser, and appears to take forever.
It has now been running for over 30 minutes and still has a status of
"executing query batch"
Is this normal?
Eric
"Hari Prasad" wrote:

> Hi,
> I recommend you to start the database in SINGLE USER mode or set the
> database to RESTRICTED mode before changing rhe schema.
>
> ALTER DATABASE <DBNAME> set SINGLE_USER
> or
> ALTER DATABASE <DBNAME> set RESTRICTED_USER
>
> Once the schema change is over you set back to multi user mode.
> ALTER DATABASE <DBNAME> set MULTI_USER
>
> --
> Thanks
> Hari
> SQL Server MVP
> "Eric" <Eric@.discussions.microsoft.com> wrote in message
> news:EE89773B-5F28-4760-B1AF-8C0347A69DF9@.microsoft.com...
>
>
|||It can be if someone is using the database. You can force
the connections to be killed with the termination clause in
the alter database:
ALTER DATABASE YourDatabase
SET SINGLE_USER WITH ROLLBACK IMMEDIATE
-Sue
On Mon, 25 Oct 2004 17:49:03 -0700, "Eric"
<Eric@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Hi Hari,
>Tried running this in the SQL Query Analyser, and appears to take forever.
>It has now been running for over 30 minutes and still has a status of
>"executing query batch"
>Is this normal?
>Eric
>
>"Hari Prasad" wrote: