Skip to main content

vCentre Useful Queries: Part II

After posting on twitter last week that I needed something to write a blog post about my good friend Christian Dadswell (Blog|Twitter) suggested I post the queries I wrote for him awhile back to dig him out of hole. Chris has dug me out of many a hole when I have needed advice on vSphere, Chris is a full time vSphere guru and part-time Android developer, which  he is very good at. Go and check out his BBC Browse Cast app for yourself. Not having an android phone myself I haven’t used his app, he refuses to get involved with Apple products which is a shame but if he gets enough encouragement I’m sure he could be persuaded. 

I have posted a query earlier this week that pulled out information from the vCentre database on VMs that had snapshots created on them that are older then 14 days. This was to allow the Sys Admins to find the snapshots before the snapshot got so big they caused issues.

Following on from this we had a bank holiday weekend (a  long weekend) and over that weekend one of the physical hosts in the vSphere stack failed. All the VMs running on the physical host HA’d and restarted on the other available physical hosts. Even though the outage was very short Chris wanted to be able to inform the business which servers would have been unavailable and hence which business services would have been affected by the outage. Unfortunately it was not obvious if the vCentre database stores this historical data (if you know otherwise please let me know in the comments) I was unable to find but it does store the current configuration. 

Chris wanted to know if there was a way to track, after the event what VMs were running on a particular physical host. In order to capture this information I needed to create table in a database that I could use to store the necessary data,  The query to pull out which VM is running on which host is as follows:

SELECT  e.NAME AS 'VirtualMACHINE',
vm.dns_name,
vm.[HOST_ID],
h.dns_name AS 'HostName'


FROM vpx_vm vm
INNER JOIN VPX_ENTITY e ON vm.id = e.id
INNER JOIN vpx_host h ON vm.HOST_ID = h.id

ORDER BY vm.HOST_ID



I then created a job to run once a day that ran the above query and inserted the results in the table created. I then developed and SSRS report that allowed a physical host and a date to be selected and the VM’s running on the host returned thus the sys admins would have a good idea of what VMs were running at a particular time and solve the above issue of what was running on what and when.


I hope you find this useful, if you have another way of doing this please do let me know in the comments

Comments

Popular posts from this blog

SQL Server 2012 and Virtual Service Accounts

This post is written by David Postlethwaite
If you are using SQL Server 2012 you will probably have noticed that the default account for the SQL services has changed from that used in previous versions. With SQL 2005 and 2008 the default account for SQL service and SQL Agent service was “NT Authority\System”. This is one the built in accounts on a Windows machine, managed by the machine and selectable from a dedicated dropdown list

The Network Service account was introduced in Windows 2003 as an alternative to using the LocalSystem account, which has full local system privileges on the local machine, a major security concern.
The Network Service has limited local privileges easing these security concerns but when many services on a machine use the Network Service account it becomes harder to track which service is actually accessing resources and performing actions, because all the services are using the one Network Service account.
Also, this account, by default, has sysadmin per…

Always Encrypted

By David Postlethwaite

Always Encrypted is new features in SQL Server 2016 and it is also available in Azure SQL Database. Here you can encrypt columns in a table with a master key and a certificate so that they will appear as encrypted strings to those who don’t have the required certificate installed on their pc.
Once the certificate is installed on the computer then the unencrypted data can then be seen as normal.

The data passes from database to your application as the encrypted value, only the application with the correct certificate can unencrypt the data so it is secure across the wire. This will go some way to resolving the concern of people worried about putting their sensitive data on a shared server in the cloud such as Microsoft Azure and accessing the data across the Internet.

At the time of writing Always Encrypted is only supported with ADO.NET 4.6, JDBC 6.0 and ODBC 13.1 but expect other driver to become available.

The calling application (including SSMS) must also hav…

New in SQL Server 2017: Graph Databases

David has recorded and published a video of his presentation on SQL Server Graph Database. In his video which you can watch below, David provides an excellent introduction into SQL Server 2017 Graph Databases. In his presentation he looks at Tennis results at tournaments for  his favourite player "The Fed"  Rodger Federer.

David  shows how to set up graph database and work with them in SQL Server 2017.

Graph Database is not new. Other vendors have had graph database capabilities for some time so Microsoft are quite late to the market. In David presentation it appears that Microsoft have done a reasonable job of implementing some of the graph database features but he does point some of the limitations of the Microsoft product too and suggests that it is not ready for production yet but Microsoft seem serious about this feature.

Please watch the video and feel free to leave a comment or feedback - David is delivering a version of this talk on Graph databases in SQL Saturday Ka…