Search results matching tags 'Indexes' and 'management studio'http://sqlblog.com/search/SearchResults.aspx?o=DateDescending&tag=Indexes,management+studio&orTags=0Search results matching tags 'Indexes' and 'management studio'en-USCommunityServer 2.1 SP2 (Build: 61129.1)Connect Digest : 2009-10-02http://sqlblog.com/blogs/aaron_bertrand/archive/2009/10/02/connect-digest-2009-10-02.aspxFri, 02 Oct 2009 15:56:00 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:17201AaronBertrand<p>Welcome to October!&nbsp; This week I have five SQL Server items to point out to you, and two Connect-specific issues.</p><p><font face="comic sans ms,sand"><font color="#336600" face="courier new,courier">/*------------------------------------------------------*/</font></font> <br></p><p><b><font size="4">&nbsp;&nbsp;&nbsp; SQL Server</font></b></p><p><font face="comic sans ms,sand"><font color="#336600" face="courier new,courier">/*------------------------------------------------------*/ </font><br></font></p><blockquote><p><a href="http://connect.microsoft.com/SQL/feedback/ViewFeedback.aspx?FeedbackID=331220" target="_blank" title="http://connect.microsoft.com/SQL/feedback/ViewFeedback.aspx?FeedbackID=331220">#331220 : Backup / Restore without index data</a><br></p><blockquote>Greg Linwood has been pushing for several items in the area of separating index data from actual data.&nbsp; One such idea is to allow backup / restore without index data (though I don't necessarily agree that one of the top reasons for implementing this would be for saving energy :-)).<br></blockquote><p><a href="http://connect.microsoft.com/SQL/feedback/ViewFeedback.aspx?FeedbackID=351043" target="_blank" title="http://connect.microsoft.com/SQL/feedback/ViewFeedback.aspx?FeedbackID=351043">#351043 : Make it possible to designate a filegroup as index-only</a></p></blockquote><blockquote><blockquote><p>This is Erland's suggestion, much in line with Greg's above, where you could indicate that a filegroup only contains index data.&nbsp; If implemented correctly, this would allow you to backup / restore the filegroup without requiring that you bring the index data along with it.<br></p></blockquote></blockquote><blockquote><p><a href="http://connect.microsoft.com/SQL/feedback/ViewFeedback.aspx?FeedbackID=377038" title="http://connect.microsoft.com/SQL/feedback/ViewFeedback.aspx?FeedbackID=377038" target="_blank">#377038 : Log File Viewer Needs a Stop Button</a></p><blockquote><p>I'm bitten by this issue every once in a while.&nbsp; On a very busy clustered instance, with uptime in the months or more, loading the most recent SQL Server log through the UI can be very cumbersome indeed.&nbsp; Especially when you know the event you after happened today. I'd like to see a set of filter criteria *before* the load starts.<br></p></blockquote><p><a href="http://connect.microsoft.com/SQL/feedback/ViewFeedback.aspx?FeedbackID=436562" title="http://connect.microsoft.com/SQL/feedback/ViewFeedback.aspx?FeedbackID=436562" target="_blank">#436562 : sp_updatestats access denied for db_owner member</a></p><blockquote><p>It is funny that members of the db_owner role can do pretty much anything they want in the database, except update statistics.&nbsp; It would seem that the update statistics code checks to see if the caller is actually *the* owner of the database (e.g. the owner_sid column in sys.databases) as opposed to just checking if they are in the db_owner or sysadmin roles.<br></p></blockquote><p><a href="http://connect.microsoft.com/SQL/feedback/ViewFeedback.aspx?FeedbackID=492480" title="http://connect.microsoft.com/SQL/feedback/ViewFeedback.aspx?FeedbackID=492480" target="_blank">#492480 : Incorrect width for datetime2 in text mode</a></p><blockquote><p>Another issue spotted by Erland; when you use SSMS in results to text mode, displaying data from DATETIME2(3-7) results in a truncated display (as if you used DATETIME or DATETIME2(2)).&nbsp; Obviously we shouldn't see a difference in output depending on whether you use text or grid, especially when there are no carriage returns or line feeds involved.<br></p></blockquote></blockquote><p><font face="comic sans ms,sand"><font color="#336600" face="courier new,courier">/*------------------------------------------------------*/ </font></font>
</p><p><b><font size="4">&nbsp;&nbsp;&nbsp; Connect Itself<br></font></b></p><p><font face="comic sans ms,sand"><font color="#336600" face="courier new,courier">/*------------------------------------------------------*/ </font></font>
</p>
<blockquote><p><a href="http://connect.microsoft.com/Connect/feedback/ViewFeedback.aspx?FeedbackID=492411" title="http://connect.microsoft.com/Connect/feedback/ViewFeedback.aspx?FeedbackID=492411" target="_blank">#492411 : "submit feedback" button on SQL connection does not do anything</a>
</p><blockquote><p>I filed this issue when I used Connect for the first time after their changes this past weekend (which I <a href="http://sqlblog.com/blogs/aaron_bertrand/archive/2009/09/26/connect-news.aspx" title="http://sqlblog.com/blogs/aaron_bertrand/archive/2009/09/26/connect-news.aspx" target="_blank">talked about here</a>).&nbsp; Sadly, on the SQL Server connection, there is a big orange "submit feedback" button in the middle of the screen, which used to work, but now doesn't.&nbsp; If the button doesn't do anything (the reason is that search is required before actually submitting), then it should be removed.&nbsp; The page is now a mess, IMHO.<br></p></blockquote><blockquote><p>&nbsp;<a href="http://sqlblog.com/files/folders/17197/download.aspx" title="http://sqlblog.com/files/folders/17197/download.aspx" target="_blank"><img src="http://sqlblog.com/files/folders/17197/download.aspx" title="click to enlarge" alt="click to enlarge" border="1" width="393" height="324"></a></p></blockquote><p><a href="http://connect.microsoft.com/Connect/feedback/ViewFeedback.aspx?FeedbackID=493549" title="http://connect.microsoft.com/Connect/feedback/ViewFeedback.aspx?FeedbackID=493549" target="_blank">#493549 : Search only searches on exact phrase</a></p><blockquote><p>Erland makes a pretty good case demonstrating that the updates this past weekend broke the search functionality, at least on the SQL Server connection.&nbsp; Now if you enter a series of keywords to search on, it actually searches for exact phrase.&nbsp; This is not very good because you either have to make your search criteria too broad (and have to step through too many results manually) or miss results because it was too narrow. <br></p></blockquote></blockquote>