This installment of the series will look at how to get information from DriveWorks into SQL, and we will get a bit more technical and open-ended, exploring some of the more advanced tools available within Microsoft SQL Server.
Visualization can be key in helping your users understand what they are configuring and what your customers will be ordering. And while 3D is a great way to provide an unambiguous representation of a product that may not even exist yet, generating 3D content […]
The wonderful thing about design automation is that we can work with so many situations where we handle a large number of unknowns.
The frustrating thing about design automation is that we can work with so many situations where we handle a large number of unknowns.
In Part 1 of this series, we discovered that using a Microsoft SQL Server (MS SQL or SQL Server) database will provide tools to handle large data sets, small data sets, complex data sets, dynamic data sets and even data that we share with other systems. But just what are those tools? How do I leverage SQL Server to processing these types of data with DriveWorks? What keywords should I put into my search engine to learn more More MORE? That’s what we’ll answer in this column.
Database. Just seeing the word can make people want to call a consultant. Luckily, I know where you can find one. (You can’t blame a guy for trying, right?) While DriveWorks provides a tremendous amount of rule driving functionality, when it comes to crunching raw data, the undisputed ruler of that domain is the database. Well, I’m here to spill the secrets and give you the basic concepts that you need to leverage Microsoft SQL Server (aka SQL Server aka MS SQL) for your DriveWorks data.