When a development team is developing a system that requires accessing a database, it is a common practice to setup local databases on each of the development environment and populate them with all the required schema of the system so that developers can develop and test the function they implement with test data in their own database, rather than working with actual data with production database.
Upon database modeling with Visual Paradigm, you always need to connect to the database server to perform generation of your database and reverse engineering of your ER model. However, you may encounter problem in connecting to the Microsoft SQL Server, which is a great obstruction to your modeling. In this article, we will provide ways to help you to check whether your configurations for connecting to SQL Server are correct.
In relational database, records are identified by a unique value. We call this value the primary key. Some databases allow to control how this unique value is being generated by defining the sequence. In this article, we will show you how to model the sequence with Visual Paradigm and use as the ID Generator for your database tables.
When defining class model for your persistent layer, a class is defined as part of the static data model instead of controller or user interface items. And the class is directly mapped to table(s) in your database. As the class is mapped to tables, its attributes is also mapped to columns in table. In order to make the mapping work, you have to model attributes with primitive types like integer, boolean, String, etc. You cannot model the attribute as any other types which are not compatible with database.
To overcome this, you can make use of ORM User Type to define customized datatype for attributes, and persistent its value into database. This article will teach you how to use ORM User Type. Read more