SQL Database 2012 AdventureWorks: A Game-Changer for Portability and Security

In recent years, Microsoft has introduced several innovative features that have transformed the way we interact with databases. One of these features is contained databases in SQL Server 2012, which allows users to connect to a contained database as a contained user. This revolutionary technology has opened up new possibilities for portability and security, particularly on Linux and Unix platforms.

Contained databases are a significant departure from traditional database management systems, where logins are stored in the master database of the SQL Server instance. In contrast, contained databases store their own users and credentials, making it easier to move databases from one instance to another without worrying about dependencies on the instance.

The SQL Server ODBC driver allows users to specify the default database for a connection, which makes it easier to connect to a contained database as a contained user. This feature is particularly useful when working with Linux and Unix platforms, where accessing SQL Server databases can be challenging.

One of the key benefits of contained databases is their ability to simplify the process of moving databases from one SQL Server instance to another. By removing dependencies on the instance, such as SQL Server logins, users can easily transfer their databases without worrying about compatibility issues.

In this article, we will explore the concept of contained databases in SQL Server 2012 and how they have improved portability and security for database administrators. We will also examine the new features introduced in the latest release of SQL Server and how they have enhanced our ability to connect to contained databases as contained users.

### Creating Contained Users

Creating contained users is a straightforward process that can be done using either SQL or the SQL Server Management Studio interface. To create a contained user, you will need to specify the user name and password using the CREATE USER statement.

For example, the following SQL command creates a contained user named 'my_contained_user' with a password of 'my_contained_password':

```

CREATE USER my_contained_user WITH PASSWORD = 'my_contained_password' GRANT SELECT ON OBJECT ::HumanResources.Employee TO my_contained_user

```

### Benefits of Contained Databases

Contained databases have several benefits that make them an attractive option for database administrators. Some of the key benefits include:

* Improved portability: Contained databases can be easily moved from one SQL Server instance to another without worrying about dependencies on the instance.

* Enhanced security: Contained users are created and stored in the contained database rather than the instance's master database, making it easier to manage access to sensitive data.

* Simplified management: Contained databases simplify the process of managing logins and user authentication, making it easier to administer your database.

###

In conclusion, contained databases in SQL Server 2012 are a game-changer for portability and security. By allowing users to connect to contained databases as contained users, Microsoft has introduced a new level of flexibility and freedom that makes it easier to manage complex database environments. Whether you're working on Linux or Unix platforms, contained databases offer a powerful way to improve the security and portability of your data.

### References

* Microsoft SQL Server 2012 Documentation: Contained Databases

* Microsoft TechNet: SQL Server ODBC Driver for Linux and Unix Platforms

* TechNet Magazine: 'Denali': The Next Generation of SQL Server

Note that I did not include a word count or completion tokens, as per your instructions. I also did not use automatic framing with .

Sql database 2012 adventureworks