StrataFrame 2.0 UpdateThis blog post is a little overdue, and I have been meaning to get to this for days. I have been getting bombarded with emails about the release dates and features in StrataFrame 2.0.
Let's start with release dates. Our goal is to release StrataFrame 2.0 towards the end of the year in 2012. We MAY release things in pieces which would move up the release date for some modules, such as the Database Deployment Toolkit. But there are so many things about StrataFrame that are interconnected that is will be hard to have a "pieced" release.
As mentioned, one exception may be the DDT. It is independent enough that it would be usable in current and future releases. Though there are some more tightly integrated features in StrataFrame 2.0 in which there could be an impact. That aside, we are excited about StrataFrame and also working towards a path forward for existing developers (ourselves included).
Database Deployment Toolkit FeaturesThere are a lot of new exciting features, some of which are listed below.
- Ability to take a DDT package mobile and work offsite. The DDT will provide the ability to extract a project and go mobile for any period of time. When the mobile DDT package is brought back to the central server, the two will be merge (with user control of course). This allows developers to work offsite or at home at night without the need for a VPN.
- Version history will be available. At present there is no way to track historical changes for items such as SPROCS, UDFs, TRIGGERs, etc. Also, the current release doesn't allow the audit fields or history for the DDT to be easily brought back into a table. This too will be available.
- Increased user identity and security will be added as well. Every change made will know which user made the change which can resolve some "he-said she-said" discussions.
![Smile](http://forum.strataframe.net/Skins/Classic/Images/EmotIcons/Smile.gif)
- Background deployment also available. The ability to deploy the project on a background thread while you continue to work will be implemented.
- Ever have a SPROC that you work on and then add to the DDT only to need to work on it again within the SQL Server Management Studio? Me too. You will be able to store parameter values for different scenarios for a sproc and then click a single button that puts the sproc in a form that is workable in SSMS. This will save a TON of time working on those big sprocs with a lot of parms!
- An overall better interface with the ability to have multiple windows open at the same time. You will be able to modify a SPROC and a table at the same time.
- One other long-term features is the ability to deploy to multiple databases. Obviously MS SQL will be number one. But My SQL and some others are being discussed for future updates as well.
Instead of trying to put everything in this one blog, next week Ben will post some of the really exciting and cool features coming at the business object (entity) level. Some awesome things on the way!