In Asia: Mazagon Dock Limited, SBM Malaysia, SDARI China, etc. In Europe: Statoil, Aircraft Carrier Alliance, Rolls-Royce Marine, Ulstein Design, Navantia, GVA, Bassoe Tech., etc. Sales worldwide 150 licenses sold, to 50 different companies, in 14 different countries, on 4 continents In the US: NNS, BIW, ExxonMobil, SBM Atlantia, KBR, EB, NASSCO, MMC, VT Halter, Austal, Textron, etc. If this post has helped you, consider buying me a coffee to say thanks.Presentation on theme: "ShipWeight Presentation"- Presentation transcript:Ģ ShipWeight More than 18 years of weight engineering in the ship and oil offshore industry ShipWeight: Weight & CG Estimation Weight & CG Tracking Weight & CG Monitoring Weight & CG During Operation In use at shipyards, design firms, and navies all over the world Used for a large variety of vessels, including naval vessels (aircraft carriers, submarines, destroyers, etc.), offshore vessels (FPSO’s, Semi-submersibles, etc.) to commercial ships (tankers, cruise and fishing vessels, etc.) Still, as you can see it’s an easy to process to export your Extended Events data to a table so you can do your analysis there – rather than having to resort to querying XML. Yes, maybe it’s my fault for capturing so many events, but in my defence, I’m trying to do some analysis in a dev environment to work out what I can filter out safely, before passing the same session to a client to use in production to diagnose the problem with a long running SSIS package. With 8 million records that’s taken 21 minutes so far.
I thought I’d knock this post together while waiting for my statement to complete which alters database_name to the preferred nvarchar(128). That’s one thing that Profiler did better, for instance database_name captured from Profiler would have been an nvarchar (128). Apart from anything else this means you can’t index the columns without changing the data type. One gripe I have with this functionality, and that you can see above, is that all the text columns come out defined as nvarchar(max). Once the export has finished you end up with a table that looks a bit like this (the exact set of columns will depend on which fields you have collected): If you look closely in the above screenshot you can see I have over 8 million events captured by this session, so it took a while to load before I was able to export. If the option is greyed out when you open the menu it may be that your event data is still loading. I’ve fallen for that and overwritten the data in a table with the same filename on a different SQL instance – whoops! Be warned that it doesn’t default to the current database connection.
You just need to select a destination database connection and table name and the export starts. If you open that and browse down, you can quickly find the option to export the results to a table: Once you’ve opened the session to view the data you get an extra drop-down menu “Extended Events” on the menu bar in SSMS. Well, with Extended Events (XE) it’s easy to do that too. If you’re a long time Profiler user like me then you probably often take the option of saving (or loading) your trace results to a table for easy analysis.
0 kommentar(er)
