Maybe you’ve been using ER/Studio for years, maybe you’re just getting started. Maybe you don’t even know where to start. You might be a full time data architect or an accidental database designer – either way, you’ll want to know about the settings and features to make your Mondays more tolerable and your Fridays more fun.
In this session, Karen covers her 10 favorite tips and tricks for working with ER/Studio. We’ll look at how to configure ER/Studio to save time, reduce risks and to make your data modeler life less stressful. She will show you features that will make your models more loved and valued by your IT and business team members.
Finally, we’ll wrap up with recommendations for more resources for becoming more productive.
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 conducted a Twitter poll last week about how to spell DATATYPE (or is it DATA TYPEs?). Many compound words start out as two separate words, then get hyphenated, then concatenated to a new word. We saw this with:
data base –> data-base –> database
I keep seeing data types spelled both ways (and never as data-type).
Ted Codd used DATA TYPE in his 12 Rules for a Relational Database Product.
Embarcadero ER/Studio and CA ERwin Data Modeler use DATATYPE in their products and occasionally use DATA TYPE in their help or documentation.
Oracle uses both spellings in their documentation. Microsoft sticks heavily to DATA TYPE.
Twitter polls last for 24 hours and not all clients can see or vote on them. So consider this more of a fun question on social media.
How do you spell this concept? Are there other words you find with a variety of spellings?
This news arrived today:
Jefferies is also leading a US$425m covenant-lite credit to back Idera’s acquisition of Embarcadero Technologies. Idera is backed by TA Associates. The deal, which launches on Thursday, includes a US$25m revolving credit, a US$300m first-lien term loan and a US$100m second-lien term loan.
So last year we had Embarcadero attempting to purchase ERwin from CA, now today we have Idera, makers of SQL Server focused database-related solutions, moving towards buying Embarcadero.
The Embarcadero-buying-ERwin deal fell through, in part, due to regulatory concerns over market consolidation of the database/data modeling tool business. I’m wondering how regulators will feel about this consolidation of tools.
I’ve worked with both vendors in the past. Both are based in Austin, Tx. Standing by to see what happens next.
UPDATE: I’m now seeing official communications about the sale, with a very aggressive closing date. This is in contrast to the prolonged, ultimately failed acquisition attempt by Embarcadero for CA’s ERwin Data Modeler product.
Thoma Bravo, a leading private equity investment firm, today announces the sale of Embarcadero Technologies, a leading provider of software solutions for application and database development, to Idera, Inc., an application and server management software provider. The exit represents the culmination of a long and successful partnership between Thoma Bravo and Embarcadero Technologies. The deal is expected to close in mid-October, subject to normal closing conditions and approvals.
I’m moderating a panel on BI, Data Governance and Data Modeling using Embarcadero ER/Studio on 16 November 2011, at noon EST.
- Kevin Phelps – Data Architect, American Century Investments, Inc.,
- Chris Bradley, Business Consulting Director, Information Processing Limited
- Jason Tiret – Director of Modeling and Architecture Solutions, Embarcadero Technologies
In this webinar, you’ll learn how to:
- Increase visibility and buy-in with business users
- Ensure smooth compliance with changing data privacy regulations
- Enable data stewards to meet requirements strategically
What makes this even more interesting is that audience members, like you, will have a chance to submit questions beforehand and during the event.
Details of the event:
Wednesday, November 16, 2011
9 a.m. Pacific, noon Eastern and 5 p.m. in the UK
When you register you’ll be asked to submit your questions. Please do so. We love having questions from YOU!
I’m deeming the hashtag for this event to be #DMExperts I will try to take Tweeted questions, too.
On Wednesday 16 February at 11 AM PST / 2PM EST I’ll be moderating a virtual Roundtable on Enterprise Data Modeling for Embarcadero Technologies. This event is primarily an attendee-driven question and answer format – no bullet points and no canned speeches. Just questions you submit and witty answers from me and my panelists:
Walt Disney Company
Matt Estes, Director Data Architecture
Jeff Pekrul, Senior Data Architect and Technical Lead
This event is free, but you’ll need to pre-register. During the registration process you’ll be asked to submit your questions for the event.
Matt, Jeff and I are looking forward to seeing your questions. Bring them on!
In working with Embarcadero ER/Studio (currently branded as ER/Studio XE), I often find that accidental system admins are confused by what appear to be duplicate or overlapping set up steps to get someone up and running with ER/Studio and the ER/Studio Repository. This is especially confusing if the admin does this only a few times a year or does not have a documented process for setting up accounts.
Before getting into the details, let’s first define some of the terms for this how-to:
Embarcadero License Server: An application that runs on a server for managing the allocation of licenses for users of the ER/Studio suite of tools, including ER/Studio Data Architect, ER/Studio Business Architect, ER/Studio Software Architect, and Schema Validator. If you have concurrent licensing for ER/Studio, you must use the License Server to hand out licenses and keep track of how many are being used. Other licensing schemes may or may not make use of the License Server.
ER/Studio Repository: An application that runs on a server for managing versioning and releases of ER/Studio Data and Process models. This is the service that allows you to check out a model and check it back in.
While the ER/Studio client can be deployed without these other services, enterprises typically deploy both the License Server and the Repository to help manage the complexity of enterprise projects. However, to most modelers, it’s all magic to them: they run their local copy of ER/Studio and all these services work together seamlessly.
So when a user needs to be set up, they may need something to be set up in two locations:
- The License Server
- The Repository
And that’s where the confusion sets in, as it can appear they are having to set up users in duplicate. It is even more confusing because organizations can customize how they manage licenses (letting anyone who has network to use a license, limiting licenses to specific machines or login IDs, etc.) So I’ll leave the exact set up steps for another post. In my diagram above, that license server uses a concurrent user list to manage which machine logins (not ER/Studio logins, but Windows User Accounts) are allowed to use a license. Your licensing scheme may be different.
The reason why users, accounts, or machines must be set up in the License server is that this services provides licenses for each of the ER/Studio suite of tools, not just ER/Studio Data Architect. It’s also because an organization could deploy ER/Studio clients without the Repository or without the License Server. They are two different services that can be used independently from each other.
Once an ER/Studio client application has obtained a license, a user can start working with models. If that user is going to access the Repository, they need to have a login and a password in the Repository application. Note that this is different than any data that was provided to the License Server.
To set up a Repository Account in ER/Studio Data Architect:
- Run ER/Studio client.
- Choose Repository from the menu bar, then Security and Security Center
- You will be presented with the Security Center window. Click on the Manage Users Tab.
- Add the new User here. You will want to use your organization’s standards for login IDs and passwords.
- Once a User has been added, he can be assigned access to certain projects and diagrams via roles.
Once you have completed BOTH allowing the user to get a license (via the License Server) and set them up with a login (User Account) in ER/Studio Data Architect, they should be ready to work.
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