Offical team blog for SSDT, a tool for on and off-premise database development
I’m pleased to announce the latest release of SSDT Power Tools. As noted previously we are using power tools to get early versions of experiences to you because we’re interested in hearing your feedback. This release of the tools builds on the previous release.
Edit: SSDT Power Tools are no longer available the link above, but have been integrated into the core SSDT product in the December 2012 release (http://blogs.msdn.com/b/ssdt/archive/2012/12/13/available-today-ssdt-december-2012.aspx)
Based on your feedback we have added “Script As…” in SQL Server Object Explorer (SSOX) to help you generate Create, Alter, Drop, and Drop and Create-To script from your connected databases.
Second, we added the ability to group by Schema, then by object type in Schema View:
Also, we added the ability to filter out built-in and external types in Schema View. Here’s the same database as above with Built-In objects hidden:
Additionally, we’ve made it easier to find the file for a specific object in your project. Now you can just right-click on the object in Schema View and choose “Select in Solution Explorer to be taken directly to the file containing your object.
Also, we added the ability to compare schema directly from Database nodes.
Installing and upgrading SSDT Power Tools:
This is designed for VS 2010 Integrated Shell and Pro + SKU with SSDT installed. If you haven’t already got SSDT, you can grab it for free on our site.
As updates to the Power Tools are released, you will need to uninstall the previous version of the Power Tools before installing the new one. You can do this from the Tools Menu. Click the “Extension Manager” option, then Click The “Uninstall” button.
This is due to a known issue in comparing the signatures of the extensions (http://support.microsoft.com/kb/2581019).
Send us feedback!
We’ve still got more goodies planned in this space including auto-refresh as Janet mentioned, but we want to hear what you think. Please let us know what you think via the "Q and A" tab of our gallery page or on our team forum. We look forward to hearing from you!
Not bad. When you group tables by schema, there shouldn't be present any system schemas without any user tables inside (db_accessadmin, gues, INFORMATION_SCHEMA etc.). In the example above there should only be: dbo, HumanResources, Person, Production, Purchasing and Sales!
If I understand what you're looking trying to do, you can get what you want in the following way:
1) Click the Group by Schema button
2) Click the filter button and Uncheck the "Show Built-in Objects" option
That being said, I'll try to think of ways to improve the usability of this so it's easier to find in the future.
It seems that I was able to upgrade from within VS. I show the latest version. Is that an error in the reporting or did something get fixed to allow updates to this extension from within VS2010?
First off, I'm glad it worked for you, but I need a little more information to answer for sure. As far as I know, there was not a fix released for this.
If you want me to look in to it, I'd be happy to do so if you can provide me with some details of the steps you took and some info your environment (OS, patch level of VS, anything else you can tell me).
Thanks for checking out our tools!
Sam, nothing unusual here. Windows 7 Enterprise 64-bit SP1, VS2010 SP1, was on v1.1 and decided to just upgrade because I couldn't remember which extension had issues with the upgrade. It did its thing, said I needed to restart to finish, and now shows in the list as v1.2. I didn't encounter any visible errors along the way. That doesn't mean that I didn't hit one, just that it didn't seem to throw any errors.
We had another thought.
It may be that you have installed the hotfix (DevDiv952740), which is the alternate work around in this article:
Definitely possible. It could easily have been pushed through our WSUS server or I could have done it manually some time back. Not 100% sure on that now. It would definitely make more sense.
This is awesome and with the new functionality I will now start actually using this in real life.
A few things that leap out at me at first glance
1. It seems the Script-As functionality is not available for tables under the Projects superfolder (only in SQL Server). Any chance of this being extended to this as this would be extremely useful for rapid development.
2. I am publishing a dacpac with a bunch of generic sql sp udfs etc that developers can include as a same database, same server dependency. Any chance that SQL Server Object Explorer could allow adding dacpac's for browsiing the objects?
3. Would be good if there was an option to hide folders with no objects in (and perhaps an indicator/count of how many objects are in each) - save on clicking and aid browsing an unfamiliar project.
4. msdb/master objects don't seem to be considered built-in objects? With a project including msdb and removing show built in objects, I still get all the standard msdb. Perhaps the ability to control this per dependency would be good (or even have another filter that split per database reference alongside split by schema). Often I would like to view non-system objects but not master / msdb.
Perhaps this would solve my point 2 if solved in certain ways?
5. A way to have the object in Object Explorer automatically/manually selected upon the current file, or by context menu click (kind-of the reverse of showing in solution explorer).
It would be nice to be able to open the source file of the object selected in the schema compare.
I often see a change and would like to edit it for some reason but need to find the source file manually instead of just right-clicking.
Opening an object from Schema Compare is indeed on our radar for a future release, although I can't say exactly when it will be.
These are on my list for the future, but I like some of the tweaks... I'll spend some time with my UX guy to see if we can work some of these ideas in!