The last couple of weekends have afforded me some SERIOUS VMware Home Lab time and out of that is a few blog posts around what I’ve been up to. In one of my prior blog posts I spoke about my new home lab (still working on that blog) and my endeavor to install everything from scratch. It also motivated me to get outside of my comfort zone and install SQL 2008 R2 for all the stuff that VMware requires its use of. The first thing on my list to add into my new SQL Database was VMware View 5. This blog post will take you through the first part of creating the database that view 5 needs. Let’s get started !!
So the install of Microsoft SQL 2008 R2 should have been easy!! Now the next step is to create the VMware View 5 database that View 5 will use. This step by step guide will help you get this setup in your VMware vSphere 5 home lab.
1. RDP into your SQL Server and click on Start, Programs, SQL Server Management Studio
2. Next just click connect – keep defaults in my case.
3. Once that opens, expand the database folder, then right click on it and choose “New database”
4. Name your database, in this case I wanted to keep it easy so I named it VMwareView5
5. Based on some reading around, I then clicked on Options and chose to change the recovery model to Simple – my understanding is it will cut down on disk space etc. Fingers crossed I don’t regret this down the road !!
6. Next thing I did was create a new role under Security. You will need a local SQL Account and not your Domain ID so this is where we would create a new local account. In this case, expand Security, expand Logins and right click to create a new Login.
7. I created a new local user and setup the password for it (it looks greyed out – that’s a screen shot issue you won’t see)– UPDATE: PLEASE uncheck enforce password expiration – Click OK
8. Now right click on that new user and go to properties
9. Then give them rights to the View 5 DB as well as make them the DB owner.
10. And we are done. You can see the DB we created (VMwareView5) as well as the new local user we created.
That’s it !! Everything should be good to go. The next step is to go and “Setup ODBC connection for View 5 inside vCenter 5” for VMware View to use.
If you have any questions, feel free to leave a comment.
11 thoughts on “Creating View 5 Database in SQL Server 2008 R2”
First things first, i need to see its a great “how to” ! A recommendation for every wane.
But i noticed 1 little thing that is when you create your user, the “User must change password at next login” is normally enabled.
This need to be off or else you can’t connect.
Thank you for the comment and you are right. It needs to be unchecked and make sure you check “password never expires”. I ran into that last one a few weeks ago when my View system stopped working !! It took a little digging around to figure out that my SQL username password expired 😦
Thanks again for the comment !!
on my case, i had to user .VIM_SQLEXP as server name to log in
Your tutorial really helped me through understanding the VMWare process…
Once thing that I would add is that in addition to adding a user to the global logins, that the user also needs to be added the the Database that we created. I don’t think this is an issue for SQL 2005, but in SQL 2008 the security is much more specific.
You may also want to consider changing the default database for the view5service account to be: VMwareview5
I encountered an error during the vCenter setup after these instructions involving permissions of the view5service account on the database. This article – http://www.boche.net/blog/index.php/2011/08/20/vcenter-server-5-0-and-ms-sql-database-permissions/ had me change the db_owner on the msdb mapping and I was able to proceed.
i had a prolems with connect odbc at vcenter, i try to troubleshoot like u write at article but everything same , after that my vcenter disconnect and i can’t to reconnect with it although i was edit like previous at protocol for VIM_SQLEXP,
Dude, thanks for the great documentation! I was banging my head against the wall trying to authenticate with a domain account and getting no where!!