I was preparing for my webinar tomorrow for Idera when I decided to look up how long ER/Studio Data Architect has been around. I was happy to see that the press release for ER/1 (what it was called before they got in a bit of a trademark issue with ERwin* folks) that it was released on 15 March 2006.
I started using ER/1 not too long after that.
Some Interesting ER/Studio Trivia
- ER/1 listed for $1399 a seat, but there was a special deal for a few months to get it for $899.
- It could handle “hundreds of entities”
- It did not feature bi-directional updating of Logical to Physical
- It did not yet feature on diagram editing
- You can still download the Documentation for ER/1 1.0
- it supported:
- Oracle 7
- Sybase 11 and 10
- Microsoft SQL Server 6
- SQL Anywhere
- SQL Base
- “ER/1 can x-ray your databases and extract their structure” < Love this.
- It followed IDEF1X methodology adopted as part of the Federal Information Processing Standards
- Submodelling (Subject areas diagramming) was not supported yet.
- There was a separate product ER/1 for Borland Interbase
March 15, 1996
Embarcadero Technologies Ships ER/1 Data Modeling Tool
San Francisco, CA, March 15, 1996, Embarcadero Technologies today announced the general availability of ER/1, a new visual, entity-relationship modeling tool. ER/1 supports all major SQL database platforms, including Oracle7, Sybase 11 and 10, Microsoft SQL Server 6, Informix, DB2, SQL Anywhere, Watcom and SQL Base.
ER/1 delivers a slew of features that promote high-quality, functionally correct data models as well as unparalleled power, ease-of use and value. Its highly customizable design allows you to create visually appealing diagrams with such tools as dockable toolbars, diagram zooming, and print scaling. Powerful inheritance logic is built into ER/1 providing referential integrity throughout your data model. In addition, ER/1 provides you with the following major features to facilitate the creation of both logical and physical designs:
Accurate and Quick Reverse Engineering
ER/1 x-rays your databases and extracts their structure into entity-relationship diagrams capturing the complete definition of your tables, including constraints, primary keys, foreign keys, indexes, table and column comments and all table dependencies.
Automatic Database Builds
ER/1 uses an ODBC connection to create a physical implementation of the logical database design you created in ER/1. This one-step process involves the creation of tables, indexes, triggers, stored procedures, views, defaults, rules and user datatypes and properly orders the creation of these objects to eliminate dependency errors.
This feature promotes code-reuse by providing a central repository to store rules, defaults, and user-defined datatypes. Once you establish a business rule as a Data Dictionary object, it is re-usable throughout your diagram. In addition, the Data Dictionary supports global updates of
these objects. Just make the change once in the dictionary and ER/1 automatically propagates these changes throughout your diagram.
ER/1 offers the most comprehensive reporting of any data modeling tool. It completely documents both your logical and physical designs and generates professionally formatted and structured reports at the summary or detail level.
Code Generation for Team Development
ER/1 can write SQL source code files ready for version control and team development. To facilitate team programming, you can generate separate source code files.
ER/1 for Windows 95 and Windows NT is priced at $1399 per user. Through April 30, 1996, Embarcadero Technologies is offering a special introductory price of only $899 per user.
About Embarcadero Technologies, Inc.:
Embarcadero Technologies is a software products company specializing in tools to design, create, administer, query, program and monitor Oracle, Sybase, Microsoft, and Informix databases. Embarcadero offers a suite of products marketed to corporate customers and database professionals worldwide and has rapidly become the leading provider of database administration tools for Sybase and Microsoft SQL Server. Embarcadero’s software has been recognized for excellence with outstanding independent product reviews conducted by PC Week, DBMS, Microsoft BackOffice Magazine and Databased Advisor.
Data Modeling Tools are Experienced
One of the reasons why some people find data modeling tools overwhelming is that they’ve been around for more than 20 years. That’s a long time for these tools to get more customized, more feature-rich, more complex.
I should give a shout out to Greg Keller, who was the product manager during the time I started using ER/Studio.
So happy birthday, Embarcadero…I mean…Idera…ER/1….ER/Studio. I’m going to have a cupcake in your honor! Maybe twenty.
*Say “ER One” Then say “ER WIN”. Yeah, almost a SOUNDEX trademark issue.
I’m visiting Dallas this week to speak at the North Texas SQL Server User Group this Thursday. I’ll be speaking about keys: primary keys, surrogate keys, clustered keys, GUIDs, SEQUENCEs, alternate keys…well, there’s a lot to cover about such a simple topic. The reason I put this presentation together is I see a lot of confusion about these topics. Some of it’s about terminology (“I can’t find anything about alternate keys in SQL Server…what the heck is that, anyway”), some of it is misunderstandings (“what do you mean IDENTITIES aren’t unique! of course they are…they are primary keys!”), some of it is just new (“Why the heck would anyone want to use a SEQUENCE?”).
We’ll be chatting about all these questions and more on Thursday, 17 March at the Microsoft venue in Irving, Texas starting at 6PM.
Attendance is free, but you need to register at http://northtexas.sqlpass.org/ to help organizers plan for the event.
Don’t worry if you don’t know about SQL Server or don’t use it: this presentation will focus on some SQL Server specific features, but the discussion is completely portable to other DBMSs.
So many of us have learned database design approaches from working with one database or data technology. We may have used only one data modeling or development tool. That means our vocabularies around identifiers and keys tend to be product specific. Do you know the difference between a unique index and a unique key? What about the difference between RI, FK and AK? These concepts span data activities and it’s important that your team understand each other and where they, their tools and approaches need to support these features. We’ll look at the generic and proprietary terms for these concepts, as well as where they fit in the database design process. We’ll also look at implementation options in SQL Server and other DBMSs.
Hope to see you there!
CA has completed the sale of the ERwin data modeling business to Parallax Capital Partners, a private equity firm with an exceptional track record of transitioning divisions, subsidiaries and product lines into successful stand-alone entities.
The transaction, which closed on February 29, is a win-win scenario that was carefully designed to ensure mutual value and a seamless transition for customers, partners, and each of the approximately 60 ERwin employees worldwide. This move also aligns with our global partner strategy, which is an important component to CA’s growth model.
With this divestiture, ERwin is an independent company that will continue to be led by its current management team.
Parallax Capital is a private equity firm that specializes in lower middle market (between $5 and $100 million) software companies. In looking at their current portfolio, I recognize only a couple of companies, with Micro Focus being the one that I recognized instantly, but they sold that in the early 2000s. Parallax owns a diverse set of companies, so I’m not sure where they will go with the ERwin Modeling product set.
What I do know is that CA was clear after the failed Embarcadero purchase attempt that they were still intending to sell off ERwin, so a purchase is important to the ERwin user market. I have no other information and expect that initial communications will be that everything is remaining the same until it changes.
This quote: “This move also aligns with our global partner strategy, which is an important component to CA’s growth model. “ appears to imply that CA did not consider data modeling a growth area of the enterprise software business. As sad as that is, I agree.
My initial feelings are that having the ERwin business owned by an entity that does not own a competing product is likely best for customers. Competition is good, for technical quality, innovation and pricing.
UPDATE: a new, more upbeat announcement has gone up on ERwin.com http://erwin.com/resources/news/erwin-divested-from-ca-technologies/
What do you think the impact of this sale will be on you and the data modeling market?
Subscribe via E-mail
- September 2016
- August 2016
- June 2016
- May 2016
- April 2016
- March 2016
- February 2016
- January 2016
- December 2015
- November 2015
- September 2015
- July 2015
- June 2015
- May 2015
- April 2015
- March 2015
- February 2015
- January 2015
- December 2014
- November 2014
- October 2014
- August 2014
- July 2014
- June 2014
- May 2014
- April 2014
- March 2014
- February 2014
- January 2014
- December 2013
- November 2013
- October 2013
- September 2013
- August 2013
- July 2013
- June 2013
- May 2013
- April 2013
- March 2013
- February 2013
- January 2013
- December 2012
- November 2012
- October 2012
- September 2012
- August 2012
- July 2012
- June 2012
- May 2012
- April 2012
- March 2012
- February 2012
- January 2012
- December 2011
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- June 2011
- May 2011
- April 2011
- March 2011
- February 2011
- January 2011
- December 2010
- November 2010
- September 2010
- August 2010
- July 2010
- February 2009