|
|
|
SSC-Dedicated
           
Group: Administrators
Last Login: Today @ 2:54 PM
Points: 31,410,
Visits: 13,726
|
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Yesterday @ 5:05 PM
Points: 39,
Visits: 586
|
|
How about better admin / monitoring tools. I know that 2008 R2 is a step in the right direction with the UCP… however it is only available for customers with Enterprise… what about those with Standard.
Something like the Oracle Enterprise Manager + Diagnostic pack would be great.
Blog: http://crazyemu.wordpress.com/ Twit: @crazySQL
|
|
|
|
|
Valued Member
      
Group: General Forum Members
Last Login: Wednesday, February 06, 2013 7:09 AM
Points: 73,
Visits: 85
|
|
at the risk of sounding not very important:
I'd very much like to see 3 changes in the sql language taken from Oracle (I know, I know, I said the O word)
1. CREATE and ALTER: instead of CREATE view/table/whatever: and ALTER view/table/whatever: in 1 statement CREATE OR ALTER... (as oracle's CREATE OR REPLACE)
2. cursor functionality: instead of : declare @var1 nvarchar(10) declare cur cursor for select myColumn from myTable open cur fetch next from cur into @var1 etc, etc
this is much handier: declare cur cursor for select myColumn from myTable for rec in cur print rec.myColumnName loop
3. detecting the type from table definition eg: MyTable has a myColumn nvarchar(10) a stupid insert procedure would have to declare the paramter as nvarchar(10) eg: create myProc (@col1 nvarchar(10)) ...
--> create myProce (@col1 MyTable.MyColumn%TYPE) when the type of myColumn changes there is no need to change the procedure!
anyway, minor changes but they could make my life a bit easier
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Today @ 10:09 AM
Points: 5,266,
Visits: 11,197
|
|
This one is very basic and simple but seems a complete no-brainer to me:
the ability to specify who the owner of the jobs will be when creating\amending maintenance plans.
Then you wouldn't have to go through and amend all the job owners afterwards (and every time you amend a plan). That is sooooooo irritating.
---------------------------------------------------------------------
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Monday, May 07, 2012 9:23 AM
Points: 304,
Visits: 716
|
|
For me? Simple...
SQL Prompt and SQL Search from Redgate.
I have never understood why these great interface-enhancing, functionality-expanding, and time-saving interface features have never become a base part of SQL Server.
There's no such thing as dumb questions, only poorly thought-out answers...
|
|
|
|
|
SSC Journeyman
      
Group: General Forum Members
Last Login: Friday, May 17, 2013 9:36 AM
Points: 93,
Visits: 545
|
|
I would like to see greater admin ability at the database level - and the ability to lock that down to the server level. Many app teams want lots of abilities in their specific databases, but even in 2008, you can't give someone bulk insert privs for a DB. Server Admins manage the disk space, etc and then each database can have an admin as well.
My second choice would be able to have SQL run on Linux or some other barebones OS so the server's sole mission is running SQL.
Cheers http://twitter.com/widba http://widba.blogspot.com/
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Monday, October 10, 2011 2:00 PM
Points: 297,
Visits: 329
|
|
I think each time someone types "architecting" in an article they should have to write on a blackboard 100 times "architecting something is the same thing as designing something but the word makes me sound cool".
Damn, I hate that unnecessary non-word.
P.S. Your built in spell check flags "architecting" as wrong. It's not just me.
Student of SQL and Golf, Master of Neither
|
|
|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: Today @ 6:56 AM
Points: 479,
Visits: 1,261
|
|
My second choice would be able to have SQL run on Linux or some other barebones OS so the server's sole mission is running SQL.

That's a silly request... MS Server has improved over the years and you can tune it to support roles.
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Tuesday, May 14, 2013 5:16 AM
Points: 1,196,
Visits: 1,319
|
|
I'd like more features on SSMS
Formatting of t-sql - with the ability to alter the formatting rules Improvements in intellisense - current version is a good start, but suggests too many wrong items Code snippets Something to outline/expand statements and transactions - so you can click a +/- next to a statement to select/hide find the end etc. Search feature to find functions/procs/columns without having to query sys tables manually Ability to get object defs/create/alter/drop code from t-sql - instead of having to navigate the object browser and right-click or, if thats too much to ask, just type the name of an object, select it and get the object browser to find that object.
And intellisense when connecting to older versions - I now have 2008 - but most of my work is connected to 2005 databases - no intellisense.
|
|
|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: Wednesday, May 15, 2013 3:05 PM
Points: 2,117,
Visits: 2,209
|
|
I agree with the SSMS requests - especially built-in intellisense and SQL formatting options.
I would also add a request for some visual aids to see how healthy a database is. I know a lot of this depends on circumstances, but it would be neat to hover the cursor over a database server top-level node and see a bar graph or pie chart of used vs. free space on that server's data drive. And if you hover the cursor over a table, show the number of rows in the table. And if a table has an index with greater than a certain amount of fragmentation (or whatever other statistics would be useful), show that table in a different color - a shade of red or something like that. Similarly, it would be helpful to have a kind of top waits report node where you could see the wait types that were most experienced in a given database, possibly with a way to drill down to see what queries were involved.
I'm not saying I want SQL Server to do everything for me, and I know a lot of these things are available in third-party (and expensive) products, but it would be nice for it to tell me things it can already know on its own, to help narrow down possible issues as soon as the database GUI is brought up, if a DBA (say, for example, me ) has not yet gotten to the state of having a lot of these checks automated. SSMS seems like the best place to add these features.
Just my two cents.
Thanks, webrunner
------------------- "The chemistry must be respected." - Walter White
"A SQL query walks into a bar and sees two tables. He walks up to them and says 'Can I join you?'" Ref.: http://tkyte.blogspot.com/2009/02/sql-joke.html
|
|
|
|