![]() |
|
|
|
By: Jeremy Kadlec | Read Comments (15) | Related Tips: More > Professional Development Career |
I have personally seen the SQL Server platform serve as the basis for solving countless business, technology and user challenges by talented professionals. Sometimes the solutions are masterpieces and other times you could say the workarounds are not pretty. To me, Microsoft delivers a relatively simple platform with SQL Server to resolve a wide variety of challenges around the globe. However, I still see technology and business professionals wanting more from the product. What's on your SQL Server wish list?
Here is your opportunity to take a few minutes and think about what is missing from SQL Server and share your thoughts with the greater community. As a SQL Server DBA consultant by profession, you might be surprised by a few of my thoughts, but we want to hear from you. Take a look a my thoughts and share yours in the comments section of this tip.
Both personally and professionally, I really like to keep things simple, straightforward and avoid any sort of complexity or drama. With some aspects of SQL Server there may be too many options. I have seen a number of customers struggle with solving a problem because they are not sure which option to select. They also do not have the time to test every option. As long as the code works and performs relatively well, they move on because their task list grows by the minute. Unfortunately, this can result in performance problems in the future. One classic example is the use of IN, EXISTS, JOIN, INTERSECT, EXCEPT, etc. commands. I generally try to use simple JOINs, but that is not always possible based on the database design.
I have also seen some confusion recently with the SQL Server tool set. Who should use SQL Server Management Studio? Who should use the SQL Server Data Tools? Should we use components from a third party in SQL Server Management Studio? Should we just use a third party tool to replace the native tools all together?
Having options is generally good, but do you feel like too many options sometimes causes confusion?
Speaking of tools, I can remember the days of Query Analyzer and really loved the tool. It was simple, lightweight and did everything I needed. I like SQL Server Management Studio and use it every day. I can also understand why Microsoft is trying to have a single toolset based on Visual Studio, but I miss that simple lightweight tool to handle my core SQL Server DBA responsibilities.
I know many DBAs and Developers are looking for more bells and whistles with the tools, but I am more interested in a simple tool. What are you looking for with the SQL Server tool set?
Another area I have seen and experienced some issues with SQL Server are related to mathematical and reporting functions (User Defined | System). Some other database\reporting vendors have financial, mortgage, statistical, etc. functions included with their product. Are there functions you wish were included with SQL Server? Would they potentially benefit the entire community, your industry or your business?
With the recent tips on PowerPivot, DAX, etc. I am eager to see how business intelligence and reporting changes for all data professionals. Unfortunately, I still see confusion on the BI side of the SQL Server platform. The integration with Excel has always made a great deal of sense to me and my hope is that business intelligence and reporting is simplified by leaps and bounds with the future SQL Server platforms. How do you think the SQL Server platform can improve business intelligence even more?
Virtualization, multiple cores, multiple instances, clustering, AlwaysOn, and more have all been beneficial for a variety of infrastructure needs. Unfortunately, I am hesitant when answering any licensing questions for customers because of upgrade paths, enterprise agreements, etc. I also have customers get confused with all of the terminology and licensing implications. I guess we are coming full circle back to "simplicity". Are you struggling with SQL Server licensing? How have you simplified SQL Server licensing at your company?
| Friday, January 18, 2013 - 10:25:13 AM - Bill | Read The Tip |
|
What would be really helpful from a DBA perspective is to have a 'create new login like' command where you could just copy an existing users security settings over to a new user. This needs to include all database and object security. |
|
| Friday, January 18, 2013 - 11:19:13 AM - Jeremy Kadlec | Read The Tip |
|
Bill, That's something and thanks for sharing your thoughts. Thank you, |
|
| Friday, January 18, 2013 - 12:12:18 PM - Gene Wirchenko | Read The Tip |
| Variables that survive across a GO! I would like to be able to have a long script with all of the configuration settings up front instead of interspersed. Passing parameters to scripts would be nice, too. | |
| Friday, January 18, 2013 - 1:35:28 PM - Jeremy Kadlec | Read The Tip |
|
Gene, Great points! Thank you. Thank you, |
|
| Friday, January 18, 2013 - 4:40:49 PM - Brady | Read The Tip |
|
I would like to seperate my SQL jobs into different folders for organization purposes. Also, I wish SSRS subscriptions were easily recognizable in SQL Agent. |
|
| Saturday, January 19, 2013 - 7:53:50 AM - Jeremy Kadlec | Read The Tip |
|
Brady, Thank you for the comments. Those are good simple suggestions. Thank you, |
|
| Tuesday, January 22, 2013 - 3:47:23 PM - TimothyAWiseman | Read The Tip |
|
I have often thought tht a simple median function in SQL Server would be extremely useful. There are certainly ways to get that answer out of SQL Server right now, but they are all unnecessarily complicated for something like getting the median. (Adding mode would also likely be useful, but that has been less significant for me personally.) |
|
| Wednesday, January 23, 2013 - 11:29:50 AM - Jeremy Kadlec | Read The Tip |
|
Tim, Thank you for the feedback. I too would love some additional functions in the SQL Server engine. Thank you, |
|
| Wednesday, January 23, 2013 - 12:23:36 PM - Gene Wirchenko | Read The Tip |
| More loop types: FOR and REPEAT...UNTIL would be useful. Something to avoid cursor read repetition. Currently, one has to prime the read then repeat the read statement in the loop. | |
| Wednesday, January 23, 2013 - 2:03:54 PM - Jeremy Kadlec | Read The Tip |
|
Gene, Thank you for the feedback... Thank you, |
|
| Friday, February 22, 2013 - 11:43:55 AM - Mathew Newton | Read The Tip |
|
You don't mention here the growing relienace and use of PowerShell for automating routine tasks etc. |
|
| Friday, February 22, 2013 - 12:04:12 PM - Jeremy Kadlec | Read The Tip |
|
Mathew, That is a great point! Thank you, |
|
| Monday, February 25, 2013 - 4:04:27 PM - Mike Hayes | Read The Tip |
|
I'd like to see a SQL Formatter tool similar to Redgate SQL Prompt. This allows quick and easy reformatting of tSQL queries formatted differently than normal, or not formatted at all.
I'd also be interested in an automated GROUP BY clause generation option. For example, if I write a query similar to:
SELECT t1.F1 AS alias1 ,t1.F2 AS alias2 ,SUM(t1.F3) FROM dbo.Table1 t1 then the following would be automatically generated:
GROUP BY t1.F1 ,t1.F2 Mike Hayes There might be times when this is not what the author intended, but I would think those would be few and far between. |
|
| Tuesday, May 14, 2013 - 11:56:50 AM - Francis McFaul | Read The Tip |
|
Since I'm a Contractor, I'd like to have a way to easily export\import Toolbar Customization and Tools Options in SSMS, and to easily export\import BOL Favorities. And, Amen to Mike Hayes for mentioning a SQL Formatting tool. |
|
| Tuesday, May 14, 2013 - 12:53:29 PM - Jeremy Kadlec | Read The Tip |
|
Francis, Great idea! Thanks for sharing. Thank you, |
|
|
privacy | disclaimer | copyright | advertise | about authors | contribute | feedback | giveaways | user groups Some names and products listed are the registered trademarks of their respective owners. Edgewood Solutions LLC | MSSharePointTips.com | MSSQLTips.com |