« Insight series: expressor projects | Main | expressor at SQLSaturday Tampa »
January 20, 2010
is expressor complementary to SSIS?
Last week we had a briefing with a well-known and highly respected Microsoft SQL Server MVP, whom I won't mention by name as I haven't asked him for permission to do so.
The main goal of our meeting was to discuss our product in detail and to find out if our value proposition will resonate with SQL Server Integration Services (SSIS) customers and users.
Fortunately for us, this particular MVP felt extremely positive about expressor and said that expressor in his view is very much complementary to SSIS. By the way, the MVP entered the conversation thinking that expressor might compete with SSIS, which in his opinion would not go down well with the existing SSIS community, which generally likes SSIS and is satisfied with using it for basic ETL tasks.
So how does expressor complement SSIS? The answer is quite simple. If you or your team encounters one or more of these types of SSIS issues, expressor might very well be the solution for you:
1. You require support for team-based application development, something SSIS doesn't offer today.
2. You run into performance issues that you find hard to overcome even though you spent time optimizing your SSIS packages.
3. You find it too painful to map heterogeneous data sources, e.g. Oracle or DB2, to a SQL Server. Or you even find it hard to map data between two SQL Server databases.
4. You experience that writing and troubleshooting complex scripts in SSIS is just too hard.
These are some of the reasons why expressor can truly be a complementary product for SSIS customers. We designed and developed our product to address these types of usage, performance and complexity issues, and offer these capabilities at an affordable price, which is key to all SSIS customers.
- Michael Waclawiczek, VP marketing
Posted by expressor software at January 20, 2010 10:45 AM
