June 10th, 2009 by Jim Kidwell
What’s so sexy about SQL databases? Well, um, sexy… gosh, you’ve got me there.
While it might not be the sexiest feature of our newest upcoming release, our External Database add-on module is one that you may find critical for your organization. How can we say that it’s critical you ask? Well, ask why don’t ya?
“OK Jim, I’ll bite. Why is it critical?”
Why, I thought that you’d never ask!
SQL databases provide additional power and stability behind the Universal Type Server that is above and beyond the default native Type Server database. They do this in a variety of ways:
- With the External Database module, you can store your entire Type Server database in a Microsoft SQL Server database. This includes all users, font licenses, keywords, etc. – pretty much everything.
- External databases can run on totally separate hardware from Universal Type Server, effectively distributing your font management server across multiple machines.
- Using SQL Server can take advantage of any potential SQL database standardization of your organization.
- SQL databases can be queried and maintained using standard SQL Server maintenance utilities.
- Most importantly, organizations with large numbers of users, very large font databases, and heavy usage will see a significant performance boost with the External Database add-on module. Check out the following chart for a comparison of the native, built-in Type Server database and an implementation using an external SQL Server database.
Of course, using an external database is optional. You can run a stable and reliable Type Server with the native database. But, I’m willing to bet that many of our customers will find the External Database add-on module critical to their business.
And hey, please don’t be offended if you actually find SQL databases sexy. I guess that it’s just up to personal preference.