IBM® DataStage® is a data integration tool that helps users to design, develop and run jobs that move and transform data. At its core, the DataStage tool supports extract, transform and load (ETL) and extract, load and transform (ELT) patterns. A basic version of the software is available for on-premises deployment, and the cloud-based DataStage for IBM Cloud Pak® for Data offers automated integration capabilities in a hybrid or multicloud environment.
N/A
Azure SQL Database
Score 8.4 out of 10
N/A
Azure SQL Database is Microsoft's relational database as a service (DBaaS).
$0.50
Per Hour
Pricing
IBM DataStage
Azure SQL Database
Editions & Modules
No answers on this topic
2 vCORE
$0.5044
Per Hour
6 vCORE
$1.5131
Per Hour
10 vCORE
$2.52
Per Hour
Offerings
Pricing Offerings
IBM DataStage
Azure SQL Database
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
IBM DataStage
Azure SQL Database
Features
IBM DataStage
Azure SQL Database
Data Source Connection
Comparison of Data Source Connection features of Product A and Product B
IBM DataStage
8.1
11 Ratings
2% below category average
Azure SQL Database
-
Ratings
Connect to traditional data sources
8.411 Ratings
00 Ratings
Connecto to Big Data and NoSQL
7.910 Ratings
00 Ratings
Data Transformations
Comparison of Data Transformations features of Product A and Product B
IBM DataStage
7.7
11 Ratings
4% below category average
Azure SQL Database
-
Ratings
Simple transformations
8.011 Ratings
00 Ratings
Complex transformations
7.511 Ratings
00 Ratings
Data Modeling
Comparison of Data Modeling features of Product A and Product B
IBM DataStage
7.0
11 Ratings
11% below category average
Azure SQL Database
-
Ratings
Data model creation
6.68 Ratings
00 Ratings
Metadata management
5.010 Ratings
00 Ratings
Business rules and workflow
7.110 Ratings
00 Ratings
Collaboration
7.111 Ratings
00 Ratings
Testing and debugging
6.511 Ratings
00 Ratings
Data Governance
Comparison of Data Governance features of Product A and Product B
IBM DataStage
5.5
10 Ratings
36% below category average
Azure SQL Database
-
Ratings
Integration with data quality tools
5.510 Ratings
00 Ratings
Integration with MDM tools
5.510 Ratings
00 Ratings
Database-as-a-Service
Comparison of Database-as-a-Service features of Product A and Product B
DataStage is somewhat outdated for an ETL. I guess that's what makes it a bit lagged behind its competitors. It can be used for data processing, sure, but its performance seems to be lagging behind or quite slow given the server it is running from. I won’t depend on this application if it's handling a lot of mission-critical banking and business data.
We have found it's a great alternative for making older legacy applications work with online databases instead of only on-premises databases. We've converted over a dozen applications this way, and it has allowed our clients to have a distributed workforce using their applications without incurring the expense of a complete application rewrite.
Maintenance is always an issue, so using a cloud solution saves a lot of trouble.
On premise solutions always suffer from fragmented implementations here and there, where several "dba's" keep track of security and maintenance. With a cloud database it's much easier to keep a central overview.
Security options in SQL database are next level... data masking, hiding sensitive data where always neglected on premise, whereas you'll get this automatically in the cloud.
Technical support is a key area IBM should improve for this product. Sometimes our case is assigned to a support engineer and he has no idea of the product or services.
Provide custom reports for datastage jobs and performance such as job history reports, warning messages or error messages.
Make it fully compatible with Oracle and users can direct use of Oracle ODBC drivers instead of Data Direct driver. Same for SQL server.
One needs to be aware that some T-SQL features are simply not available.
The programmatic access to server, trace flags, hardware from within Azure SQL Database is taken away (for a good reason).
No SQL Agent so your jobs need to be orchestrated differently.
The maximum concurrent logins maybe an unexpected problem.
Sudden disconnects.
The developers and admin must study the capacity and tier usage limits https://docs.microsoft.com/en-us/azure/azure-subscription-service-limits otherwise some errors or even transaction aborts never seen before can occur.
Only one Latin Collation choice.
There is no way to debug T-SQL ( a big drawback in my point of view).
Because it is robust, and it is being continuously improved. DS is one of the most used and recognized tools in the market. Large companies have implemented it in the first instance to develop their DW, but finding the advantages it has, they could use it for other types of projects such as migrations, application feeding, etc.
The interfaces are intuitive once you are familiar with all the functions. The ability to use different tools to interact with the platform, such as directly via a browser or code editors such as VS Code or Visual Studio is a great option and allows for integrating withn the project and other testing and developing tools.
It could load thousands of records in seconds. But in the Parallel version, you need to understand how to particionate the data. If you use the algorithms erroneously, or the functionalities that it gives for the parsing of data, the performance can fall drastically, even with few records. It is necessary to have people with experience to be able to determine which algorithm to use and understand why.
IBM offers different levels of support but in my experience being and IBM shop helps to get direct support from more knowledgeable technicians from IBM. Not sure on the cost of having this kind of support, but I know there's also general support and community blogs and websites on the Internet make it easy to troubleshoot issues whenever there's need for that.
We give the support a high rating simply because every time we've had issues or questions, representatives were in contact with us quickly. Without fail, our issues/questions were handled in a timely matter. That kind of response is integral when client data integrity and availability is in question. There is also a wealth of documentation for resolving issues on your own.
With effective capabilities and easy to manipulate the features and easy to produce accurate data analytics and the Cloud services Automation, this IBM platform is more reliable and easy to document management. The features on this platform are equipped with excellent big data management and easy to provide accurate data analytics.
We moved away from Oracle and NoSQL because we had been so reliant on them for the last 25 years, the pricing was too much and we were looking for a way to cut the cord. Snowflake is just too up in the air, feels like it is soon to be just another line item to add to your Azure subscription. Azure was just priced right, easy to migrate to and plenty of resources to hire to support/maintain it. Very easy to learn, too.
It’s hard to say at this point, it delivers, but not quite as I expected. It takes a lot of resources to manage and sort this out (manpower, financial).
Definitely, I don’t have the exact numbers, but given the data it processes, it is A LOT. So props to the developer of this application.
Again, based on my experience, I’d choose other ETL apps if there is one that's more user-friendly.