RE: A couple of R2 Impressions



I agree 110% with Ross M...why why why take away my DTS that I rely and works
so well...I'd rather pay a little more and get the full featured SQL
Server...I don't use ISA and don't plant to...but I HAVE TO HAVE my DTS
component or I can't use it...it is going to be hard enough to master SQL
2005 alone, but I would do it if I had the std edition...I guess I'm not
considered SMALL if I use DTS?????????? NO UPGARDE FOR ME...

"Ross M" wrote:

Hey Garth

I'll be intersted in your impressions on the SQL 2005 implementation as I
have concern over the decision to dramatically reduce functionality with the
recent product bundling decisions in the Premium version. The decision to
downgrade the database from SQL Standard to SQL Workgroup is a retrograde
step, and will certainly prevent most of my SBS Premium customers from
upgrading. Indeed, why should they pay to have the feature set reduced!! Or
to put it another way, they have payed $400 (if they have SA, or $700 if not)
to LOOSE $700 by going from a $1,400 database to a $700 database. This is NOT
good value, or good business for MS – it just alienates customers. It is
really difficult to see how MS can justify charging for this release when it
really is just a minor upgrade that integrates an already free (WSUS)
component with a couple of dinky management reports and then reduces
functionality of a major application. Keeping the SQL Standard version would
have helped justify the price!

The main problem here is that the SQL Workgroup edition does not include the
SSIS functionality of the Standard edition. In SQL 2000 we had full access to
DTS, and most of our customers who bought the premium version did so on the
basis of having a fully featured SQL database, INCLUDING the DTS engine, to
drive bespoke applications. The DTS (renamed SSIS in SQL 2005) functions are
integral to nearly every bespoke database application we have developed and
they are used by customers who have their own development resources. However,
you have stripped this crucial functionality from the product.

I know that the DTS packages already written in SQL 2000 will function in
the Workgroup 2005 edition, but this is only a stopgap, as customers don’t
have the ability to edit these or create new functions.

I guess it is too late to do anything about this decision, but I have to say
that I am disappointed at the downgrading of what, to date, has been an
exceptional package for small businesses. I suspect this will just drive
small business customers to use SBS Standard and load MySQL or PostGress, as
there is now not any significant differentiation in the Workgroup database to
justify the Premium edition pricing. (By the way, ISA Server is not a
purchasing driver for SBS Premium in my experience; it is the database – most
customers have more than adequate hardware stateful firewalls, and these
continue to plummet in price and increase in functionality – for example high
throughput stateful firewalls for around $100 and dual WAN load balancing
firewalls with integrated 4-port FXS VoIP gateways for around $400. ISA adds
significant complexity and server overhead for little real gain, and remains
shelf-ware in most SBS installations that I see.)

I believe that this decision is short sighted. I thought that part of the
SBS rationale was to buy goodwill to small, but growing, customers so they
stay on the Microsoft path as they add infrastructure. I think this will have
the opposite effect, at least as far as the database is concerned.

.



Relevant Pages

  • Re: Foxpro sql limitations
    ... My application is an online user interface for customers to log on to ... and check the status of their fleet of vehicles (the client is a fleet ... The ASP site connects to the Foxpro database used ... This SQL db has since been expanded to include some more ...
    (microsoft.public.fox.vfp.queries-sql)
  • Re: Database terminology
    ... Jeff Boyce wrote: ... opinion which does not reflect SQL DBMS 'best practice'. ... fundamental area of Jet 4.0 functionality from an inexplicably biased ... I think it a shame when people in the Access community use language ...
    (microsoft.public.access.tablesdbdesign)
  • Re: How do I run a .BAS file saved from a DTS package?
    ... Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) ... I have used DTS for import and export. ... > The DTS Designer is easy to understand and use. ...
    (microsoft.public.sqlserver.dts)
  • Re: Modifying Data Directly through Studio Manager
    ... 'tool' to allow your customers to manage their data. ... I've seen people comment on turned on the query pane, ... Many of my customers are starting to upgrade to SQL 2005, ... Isaac Shloss, MCSE ...
    (microsoft.public.sqlserver.tools)
  • Re: Sybase Source. What "data flow source" to use?
    ... but could still use DTS to move data. ... when I right-click over a SQL 2005 database and select Import ... datasources defined in ODBC Datasources on my computer, ...
    (microsoft.public.sqlserver.dts)