Again, if you know what you're doing and where things are at and query using the most effective SQL statements, go for it, but note that you CAN impact performance on your vCenter as there are jobs that run to roll up stats/etc. I've written some stuff against the old vCenter 2.5 and most of the tables are pretty trivial to understand and using a tool like dbvisualizer, helped me poke around and figure the relationships. Unless someone here in the community fully documented and explained what every single table means/etc.
#DBVISUALIZER EXPORT FLOAT DATA WRONG FULL#
If you're developing 3rd party application, I would get a hold of VMware partner channel and perhaps they can provide you with the full schema details. I believe internally in performance API calls vcenter also access the runtime informations from its database. So I think accessing database directly (bypassing all vcenter api overhead) may give better performance. If you find this information useful, please award points for "correct" or "helpful". But setting up a vCenter connection from application to the server and fetching data through API seems to be taking a bit long time.
#DBVISUALIZER EXPORT FLOAT DATA WRONG CODE#
Twitter: Code Central - Scripts/Sample code for Developers and Administrators Pass bind parameters as Object if you want to insert an Array or BLOB or CLOB data to DB2. The BLOB data type contains varying-length binary string data with a length of u. VMware ESX/ESXi scripts and resources at: DB2 export utility can export the table data to 4 different file format: DEL : delimited ASCII format. The only other thing I could even think of, which isn't even worth it in my mind is to retrieve the actual creation date of a VM, this is something that may not be in the API depending on the amount of historical data you're archiving. Is there any reason you need to hit the database directly? One wrong SQL query and you can halt your system or create some infinite query, why chance that?Įverything that you could ever want to retrieve is available using the vSphere API and the available SDK's to retrieve this information.
This is definitely not recommended and doubt you'll find much support from VMware. I don't believe anyone has published the schema for vSphere vCenter 4.0, I know back in the day for vCenter 2.5, there was one floating around the net.