Wednesday, May 23, 2007
Wishlist of New Features, Improvements in SQL Server 2008 ("Katmai")
(Okay, so maybe it will be SQL Server 2009 but I doubt it)
Here's a wishlist of items that probably closely reflect the Microsoft Connect information. I must admit - I don't really use Microsoft Connect because I find it difficult and annoying to use the Microsoft Passport Logins - I just don't like 'em.
Here's a wishlist of items that probably closely reflect the Microsoft Connect information. I must admit - I don't really use Microsoft Connect because I find it difficult and annoying to use the Microsoft Passport Logins - I just don't like 'em.
- Intellisense in the development environment *please*
- We had it in the private betas of SQL 2005 so we know you havethe technology, MSFT
- Bring back the DATE and TIME data types as separate types
- Give us more and better standard reports built in
- The Performance Dashboard and the SQL H2 reports should be included
- Include the SQL Server Health and History tool information as native in the system
- Let me edit/author SSIS packages directly in the SSMS tool
- More wizards for the simplest operations like creating an index, database, SSIS package and make these wizards more easily located
- More user-friendly front end for new people than just the Object explorer for doing SQL management
- Script repository or some better way than the solutions in SSMS
- I like the solutions to a degree but I'd prefer server-side storage
- Better SSIS package creation and deployment
- It's not easy to figure out for a first-timer how to do *anything* in SSIS
- No more vapor ware
- There is no such thing as the "Business Intelligence Development Studio"; it's just a wrapper around the Visual Studio IDE. Why confuse people more? Just call it Visual Studio and be done with it.
- Do not follow the SharePoint team's lead and name everything SharePoint
- Quick: What's the difference between SharePoint 2007 and SharePoint 3.0 (or is there a difference)? Is there even a product named SharePoint 2007 or is it really Office SharePoint 2007? Or SharePoint Portal Server 2007?
- Enough with the "Services" already
- Database Services, Integration Services, Analysis Services, Reporting Services, Notification Services - stop!
- Settle on a name for the core SQL Server product
- I've seen it called SQL Server 2005, SQL Server Database Services, SQL Server Database Engine - which is it?
- Give us GUI interfaces to manage Notification Services
- Maintenance Plans should be easier for newbies to work with
- Asking first-timers to understand sub plans just so they can have multiple schedules is too much IMO
- Give us a dashboard-type tool that provides best practices for the various database types
- Drop down to choose "This is a SharePoint database", or "This is a Reporting Services database" or "This database is mostly read only", etc.
- Based on the choice, make recommendations for fill factors, defragment suggestions, etc
- Integrate a new version of the Best Practices Analyzer into the RTM
- Don't make us download it
- Easier ways to work with snapshots - no scripting should be required
- Easier to work with snapshot isolation level - again no scripting should be required
- In SQL 2005 Beta 1, we could drill down into objects by schema in the Object explorer - I'd like that to be an option in the next tool
- Tables -> dbo -> Table1, Table2
- Tables -> HumanResources -> Employee
- More consistent use of schemas in the tools
- The Query Designer, for example, was clearly not updated to use schemas well
- Design a better Query Designer
- MSFT ruined the Query Designer in SQL 2005 since, when you open the tool, it automatically runs a SELECT * FROM the entire table
- Let me create event alerts on system errors again
- Why was it this was removed again? Arrrrrggghhhhh
- Better integration with Active Directory for Logins
- I should be able to check a box next to a Loginand say, "Make this an operator". SQL would then have this person's email and I wouldn't have to keep my email/operators in sync with my Logins
- Better errors and screens for managing Database Mail
- It sure does have the feeling of an alpha/beta product, doesn't it?
- Better visual setup/ways to manage peer-to-peer replication (a.k.a., multi-master)
- Break down the management/catalog views better
- These long names are just killing me!
- What if, instead of just Database.schema.owner we could address items in an "infinite" namespace that the user chooses?
- SELECT * FROM MyDb.HumanResources.Employees_Archive_2006_Q2_PerformanceReports is a horrible way to name (and remember) tables/views/functions/procs
- SELECT * FROM MyDB.HumanResources.Archive.Employees.PerformanceReports.2006.Q2
- I know this isn't ANSI standard and some people may not like it but so what? I like it :)
- Give us a usable System Views map
- The current system views map for SQL Server 2005 is just not usable - I can't search for anything and it's too big to matter :(
- Make it easier for admins to sync Logins from ServerA to ServerB when restoring/attaching databases
- The current approaches create Logins with different SIDs only. I'd like the option for Logins to be identical. This is critical for disaster recovery.
- Allow me to restore a master database from one machine to another
- Again, this is critically important for disaster recovery and I should be able to do this easily
- Give me the option to create server-level roles for management
- I love the granularity of SQL 2005's server permissions but I'd prefer to do role-based management instead of Login-based management
Comments:
Links to this post:
<< Home
And what the HAY with Credential + Proxy + Login+ Permissions, just for simple package context in a job step? Did Oracle do some contract development on the SQL team? How many different things to accomplish a checkbox's worth of functionality? Sheesh.
While you're dreaming - how about client tools that are as fast as previous versions? Am I the only person who misses the simplcity of old QA? An administrator should not need a dual processor, 2GB machine to administer a SQL server.
While you're dreaming - how about client tools that are as fast as previous versions? Am I the only person who misses the simplcity of old QA? An administrator should not need a dual processor, 2GB machine to administer a SQL server.
I laughed at you comments about the speed of the tools. It's really .NET AFAIK that is the root of the problem. Every stupid button you click, anytime you right click, and basically anytime you want to do *anything*, .NET has to JIT the code to perform that action - and you have to wait, wait, wait. I'm on a 64-bit dual core machine with 2GB DDR-667 RAM and SSMS is slow to load and slow to get going. Once it goes through and JITs the code, it's awesome but man -waiting for it to JIT what I want is annoying.
I love lightweight tools but I also love heavyweight tools. I'm sort of mixed about SSMS' speed. Once you learn to speed it up it is much better.
Have you watched the videos on using SSMS on LearnSqlServer.com? I put a few speed tips - like passing in the parameters to SqlWb.exe and the whole thing with IE's publisher site revocation. Those really make it faster.
Post a Comment
I love lightweight tools but I also love heavyweight tools. I'm sort of mixed about SSMS' speed. Once you learn to speed it up it is much better.
Have you watched the videos on using SSMS on LearnSqlServer.com? I put a few speed tips - like passing in the parameters to SqlWb.exe and the whole thing with IE's publisher site revocation. Those really make it faster.
Links to this post:
<< Home
