I can't beleive I paid for this

Packages and compresses schema and contents of SQL Server databases

Moderators: JonathanWatts, Chris Auckland, David Atkinson, david connell, Anu Deshpande, Michelle Taylor, james.billings, Marianne

I can't beleive I paid for this

Postby CodeDreamer68 » Sat Feb 13, 2010 8:48 pm

I am extremely frustrated right now because I've paid for a utility that is supposed to save me time, but is actually wasting my time. That angers me greatly.

Frankly, at this point I seriously doubt that I will recommend this product for upgrade within our corporation. You can also expect me to express my complete disatisfaction with Red Gate SQL Packager on my blog as well.

You people have had plenty of time to fix the problems with your software, it was released in 2008, no?

For the record, I'll state the top 3 problems I have with your software (not that you'll do anything about it, because I've complained before, a year ago and you obviously haven't fixed it yet)

First, using the wizard, when I uncheck boxes for objects in my database, the packager seems to completely ignore my un-selections and scripts them anyway. So that means I have to go through the script, that your software generates, line-by-line and remove all the objects that I didn't want scripted.

This means I can't build an executable installer package, because your software dosn't allow you to edit the script manually, prior to creating said executable package.

Second, the script also seems to create db objects in the incorrect order, thereby causing catastrophic errors that cease the execution of the script and rollback the transaction. For example: one of my my databases has FK constraints that your tool puts BEFORE the place in the script where it actually creates the tables to which they should be attached. I have to cut and paste the sections where the tables are created so they get created PRIOR to the objects such as FK constraints, defaults, and descriptions.

Thirdly, your product does a lousy job of handling FullText catalogs. The script completely crashes when it creates stored procedures that contain any fulltext references, because those tables that were created by the script, did not get their full text indexes created yet. For some idiotic reason you decided to put all the lines of script that create the full text catalogs at the BOTTOM of the script. WTF are you thinking?


All these serious problems make me want to ask for my money back.

Your product is completely useless and has no value. If I wanted to just have some tool automatically script my database, so I would then have to go through it line-by-line, and re-script it manually... then I would have just used Visual Studio's database deployment feature.

Explain to me why anyone would buy this POS?
CodeDreamer68
 
Posts: 3
Joined: Wed Mar 25, 2009 4:57 pm

Postby Chris Auckland » Mon Feb 15, 2010 11:42 am

Thanks for your post.

I believe you have found the private release version now, so hopfully this should resolve your first issue. (Tools > Options > schema options > [uncheck] include dependencies)

When you try the patch version, can you see if using the updated SQL Comapre & SQL Data compare engines also resolves your script order issue?

With regards to the FullText catalogs, unfortunatly this is actually quite difficult to resolve.

Changes to the FULLTEXT Catalog or Indexes cannot be placed into a transaction and therefore have to be scripted somewhere outside of the transaction. If we put the full text stuff first and then there was a problem with the subsequent transaction, then the database would be left in an inconsistent state. We feel that it's better to create a script that fails and rollsback, rather then damages the database.

The usual workaround to this problem (with SQL Compare) is to compare the two data sources, synchronize the FULLTEXT Catalog first on it own, then refresh the comparison and synchronize the remaining database objects. With SQL Packager, you could use the same approach, but save a sync script for each, then join them together and use the 'package script' feature of SQL Packager 6.

I hope this is helpful.
Chris
Chris Auckland
 
Posts: 757
Joined: Tue Oct 24, 2006 2:12 pm
Location: Red Gate Software Ltd.

Re:

Postby CodeDreamer68 » Mon Feb 15, 2010 8:38 pm

Chris Auckland wrote:Thanks for your post.

I believe you have found the private release version now, so hopfully this should resolve your first issue. (Tools > Options > schema options > [uncheck] include dependencies)

When you try the patch version, can you see if using the updated SQL Comapre & SQL Data compare engines also resolves your script order issue?

With regards to the FullText catalogs, unfortunatly this is actually quite difficult to resolve.

Changes to the FULLTEXT Catalog or Indexes cannot be placed into a transaction and therefore have to be scripted somewhere outside of the transaction. If we put the full text stuff first and then there was a problem with the subsequent transaction, then the database would be left in an inconsistent state. We feel that it's better to create a script that fails and rollsback, rather then damages the database.

The usual workaround to this problem (with SQL Compare) is to compare the two data sources, synchronize the FULLTEXT Catalog first on it own, then refresh the comparison and synchronize the remaining database objects. With SQL Packager, you could use the same aproach, but save a sync script for each, then join them together and use the 'package script' feature of SQL Packager 6.

I hope this is helpful.


My needs are simple.

#1 I need to create a package that my end users can execute to install my database. I can do this manually myself, without your software.

#2 I want to save myself time. Instead of having to manually create an installer package myself, from scripts generated with either Visual Studio data tools, SQL Server Management Studio, or CodeSmith, I need a tool that is smart enough to do it for me. (That's what I was led to believe SQL Packager is)

Your product, even after your suggestions and excuses, still does not meet my needs or the needs of my corporation. As such, I cannot recommend upgrade again.
CodeDreamer68
 
Posts: 3
Joined: Wed Mar 25, 2009 4:57 pm

Same issue, where is this "private" version?

Postby rshadman » Fri Apr 09, 2010 10:51 pm

My company has just purchased this software on my recommendation and am having exactly the same issues stated in the original post, plus some more not stated related to your transactional wrapping (I get a much cleaner script if i turn off your attempts at using transactions).

Where is the version that works, and why haven't the fixes been rolled into the version you offer to download?

I need the working version as quickly as possible; please respond promptly.

EDIT:

I just saw the sticky thread with the patch, going to try it out now.

On a side note, you may be waiting for more testing before rolling out this patch, but not having a working product has cost my company an extra couple of hours of productivity due to me wasting time having to first find out the product was shipped buggy and then having to research where to find the patch. The LEAST you could do is include the information in the receipt of purchase, if you aren't willing to provide a better working copy in your trial showcase.

Perhaps it was my fault in assuming the product would work as purported to do, considering how strong some of your other products are. Next time I will fully test any product of yours before making a recommendation on purchase.
rshadman
 
Posts: 2
Joined: Fri Apr 09, 2010 10:42 pm

Postby rshadman » Fri Apr 09, 2010 11:35 pm

The upgrade solved all the dependency issues except stored procedures accessing full text catalogs. Also, the transactional features still don't work. If i disable all the transactional options, the script generates fine.as long as I exclude the stored procedures that utilize the full text catalog.

If the transactional features (and in my case it's the only way your software is useful) are disabled you shouldn't have an issue placing the full text catalog script in a better location suited to the objects dependent on them. Just a thought for your next private patch.
rshadman
 
Posts: 2
Joined: Fri Apr 09, 2010 10:42 pm

Re: I can't beleive I paid for this

Postby PlanitSoftware » Fri Jun 11, 2010 3:07 pm

CodeDreamer68 wrote:First, using the wizard, when I uncheck boxes for objects in my database, the packager seems to completely ignore my un-selections and scripts them anyway. So that means I have to go through the script, that your software generates, line-by-line and remove all the objects that I didn't want scripted.

This means I can't build an executable installer package, because your software dosn't allow you to edit the script manually, prior to creating said executable package.

...

Explain to me why anyone would buy this POS?


I am pretty horrified that our first day as a user, I have immediatly run into this really fundamental issue that doesnt seem to have been addressed, even with the patch.

Just to be clear, when I deselect User objects (because they wont exist on a customers server), they are still included in the script.

As a new purchaser of the full ToolBelt, I will not sit around until my distance selling and other rights have expired before obtaining a refund.
PlanitSoftware
 
Posts: 1
Joined: Fri Jun 11, 2010 2:58 pm


Return to SQL Packager 6

Who is online

Users browsing this forum: No registered users and 0 guests