SQlpro

My feedback

  1. 2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    SQlpro shared this idea  · 
  2. 3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    SQlpro supported this idea  · 
  3. 4 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    SQlpro commented  · 

    When encryting a database with TDE (Transparent Data Encryption) from scratch, the TDE process involve the tempdb database too.
    But this is not the case when the TDE database is restoring from another SQL Server instance, like in the AlwaysOn process to fill the secondary nodes.
    In fact the encryption of tempdb database is done when executing the T-SQL command "ALTER DATABASE ... SET ENCRYPTION ON;"

    We found a bypass to correct this lack, that consist to create a dummy database, encrypt it and drop it.

    The above script can do that

    -- verify if tempdb is encrypted :
    SELECT name, is_encrypted
    FROM sys.databases
    WHERE name = 'tempdb';
    GO

    -- create a dummy datbase to encrypt
    CREATE DATABASE dummy;
    GO

    -- encrypt it
    USE dummy;
    CREATE DATABASE ENCRYPTION KEY
    WITH ALGORITHM = AES_256
    ENCRYPTION BY SERVER CERTIFICATE my_cert_used_for_the_previous_database;
    GO
    ALTER DATABASE dummy
    SET ENCRYPTION ON;
    GO

    -- drop ti !
    USE master;
    GO
    WAITFOR DELAY '00:00:30';
    GO
    DROP DATABASE dummy;
    GO

    -- verify if tempd is now encrypted :
    SELECT name, is_encrypted
    FROM sys.databases
    WHERE name = 'tempdb';
    GO

    It will be smart if the tempdb will be encrypted when restoring an TDE encrypted database.

    SQlpro supported this idea  · 
  4. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Site Recovery  ·  Flag idea as inappropriate…  ·  Admin →
    SQlpro supported this idea  · 
    SQlpro commented  · 

    This value should be InstanceDefaultBackupPath instaed of InstanceBackupPath.

  5. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Other  ·  Flag idea as inappropriate…  ·  Admin →
    SQlpro shared this idea  · 
  6. 22 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 6

    <=-=Mar 3 2017 2:00PM=-=>

    We are aware that this is important missing feature; however, we have no plans to add this in the near future. We will keep this request in backlog to see how many votes will get.

    <=-=Jul 1 2017 7:03PM=-=>

    Can’t even remember how many times I’ve wished to have this in SQL server.

    If you want to get a somewhat realistic feel of how talked about this feature really is, you can check out the number of votes and more importantly views that this StackOverflow question has:

    https://stackoverflow.com/questions/1732613/how-to-declare-array-inside-sql-server-stored-procedure

    Unfortunately, not many people visit this website and participate in voting here so it’s not a reliable indicator of how much any particular feature is requested. Please consider moving to UserVoice. Visual Studio UserVoice for example has loads more activity.

    <=-=Jul 1 2017 11:17PM=-=>

    We totally understand that t-sql as a language itself is desigened to…

    SQlpro supported this idea  · 
  7. 27 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    SQlpro supported this idea  · 
  8. 21 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  SQL Server » Other  ·  Flag idea as inappropriate…  ·  Admin →
    SQlpro supported this idea  · 
  9. 318 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 249

    <=-=Oct 4 2016 2:15PM=-=>

    This is similar to my feedback located here: https://connect.microsoft.com/SQLServer/feedback/details/2769130/sql-2016-temporal-tables-with-triggers. The solution I suggest is similar to this, and could be used in many different cases developing using SQL server.

    <=-=Jan 10 2017 9:43AM=-=>

    I would love this too. The issue is that many/most applications don’t use Windows Auth in the connection to SQL Server (connection pooling issues, etc), so SQL can’t get the User information

    <=-=Jan 10 2017 9:51AM=-=>

    @Sanford

    Just to clarify, I am not asking for an “automatically store user name” feature. I’m asking for “automatically store whatever I want, based on whatever expression I provide.” So the fact that the user name may or may not be available is not really relevant.

    That said, there are plenty of workarounds for various situations. I imagine that if you’re using a shared connection, you can get some notion of “user” some other…

    SQlpro supported this idea  · 
  10. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 8

    <=-=Oct 10 2007 2:31AM=-=>

    This may become even more important with filestream filegroup functionality in SQL 2008, allowing to move from an internal database filegroup to the filestream filegroup will be a valuable addition.

    <=-=Feb 1 2008 10:00AM=-=>

    Thanks for your feedback. We will look into this during the planning for the next release. Your point about migrating text/image data to filestream is very compelling. Here is what you can do with SQL2008 and filestream

    Let us say you have a table table t1 (c1 int, c2 varchar(max)). Now you can do the following
    (1) add a varbinary(max) FILESTREAM column c3 and a rowguidcol column c4 to the table.
    (2) update the table setting c3 = c2. This copies the data from the database files to the external files.
    Then you can drop c2 and if you want rename c3 to c2.

    <=-=Feb 4 2008 9:26AM=-=>

    I support…

    SQlpro commented  · 

    Two ways can be used to bypass the problem :
    1) create all your tables with a dummy BLOB column and specify TEXTIMAGE_ON with a dedicated filegroup, then, alter the table and drop the dummy column. This prepare the table to have all the LOBs stored into the dedicated FG.
    2) alter the table so that it is partitioned in an unique partition stored on the dedicated BLOB filegroup, and then remove the partition by creating the clustered index on the original FG

    SQlpro supported this idea  · 
  11. 4 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 371

    <=-=Feb 10 2010 1:31PM=-=>

    What a great suggestion – this would make writing clearer and more self-documenting code so much easier.

    <=-=Feb 15 2010 7:53AM=-=>

    I do these kinds of ROW_NUMBER() queries ALL the time. This would be a wonderful option. Please give this serious consideration. It would make my code much cleaner.

    <=-=Feb 16 2010 7:12AM=-=>

    This would be extremely useful. The OVER clause was really handy, but the CTE is a necessary evil if you want to get the most use out of row_number(). You have my vote.

    Thanks,
    Eric

    <=-=Feb 17 2010 4:09PM=-=>

    Hi Itzik,

    Thank you for your suggestion! This does sound like a very useful addition to T-SQL. We will be triaging the request and see if it can make it into a future release of SQL Server.

    Again, thanks for your feedback!
    - Tobias, SQL Server Engine

    <=-=Mar 2 2010…
    SQlpro supported this idea  · 
  12. 8 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 23

    <=-=Oct 19 2015 2:55PM=-=>

    We recently had discussion about dropping unused indexes and during the discussion, a question came up about few indexes on whether they were created recently or did they exists for a while and I have no easy way to answer that question.

    SQlpro commented  · 

    There is almost 4 entries of the same topic :
    1 - Expose index creation date in sys.indexes
    2 - Report Index creation time and modification time
    3 - Add create_date and modify_date to sys.indexes
    4 - Add sys.indexes create_date and modify_date fields

    Adding the creation and last rebuild date would be a very important feature in the implementation of indexing campaigns. This would make it possible to decide whether an index should be deleted or not. Currently the view sys. DM _ db_index_usage_stats allows to know whether an index is used or not (User_seeks, User_scans, User_lookups...). But as we do not know if it was created recently or exists since a long time, this information is, in fact, of no value!

    SQlpro supported this idea  · 
  13. 2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 28

    <=-=Jan 15 2009 2:43PM=-=>

    Hi Brian,
    Thanks for your request. We are aware of your ask and we will consider it for a future version of SQL Server. For now, you can create DDL trigger and track the index creation/alter in your own tables. This will allow you to get the information you are looking for.


    Umachandar, SQL Programmability Team

    <=-=Dec 3 2009 7:55AM=-=>

    I’d also like to throw some support around this as something to include in the next version of SQL Server

    <=-=Dec 3 2009 7:59AM=-=>

    I’d like to see thes as well. I’d also add that seeing last rebuild date and last reorg date would be helpful as well, even if they were via function like STATS_DATE().

    <=-=Dec 3 2009 8:04AM=-=>

    Upvoted as I think this is definitely something that needs to be added. In addition to adding this, please add a related report…

    SQlpro supported this idea  · 
  14. 5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    SQlpro supported this idea  · 
  15. 2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 2

    <=-=Mar 30 2010 6:12PM=-=>

    Thanks for your suggestion. For now, the work around is to create DDL trigger and track the index creation/alter in your own tables. This will allow you to get the information you are looking for.

    I will mark this item as closed as there is already an item with connect-id (feedback-id) 394870

    Thanks
    Sunil

    SQlpro supported this idea  · 
  16. 36 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    SQlpro commented  · 

    It would be great if such a formatter can provide an indentation of join like a hierarchical tree

    SQlpro supported this idea  · 
  17. 7 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 17

    <=-=Mar 9 2014 4:32PM=-=>

    This issue has a critical performance impact on large DB optimization. Actually it would be good to have cardinality hint on any table in query, or at least temp table.
    The reason is this connect issue – https://connect.microsoft.com/SQLServer/feedback/details/758241/update-statistics-does-not-cause-recompilation-for-a-cached-temporary-table
    The hint should take local variable as input, not only literal.

    <=-=Mar 23 2015 8:39AM=-=>

    Having a local variable causes the issue that you don’t have the amount when the plan is made when a procedure execution starts — but at least I would really love to see even a hint with fixed number, similarly to “optimize for” -hint.

    <=-=Jun 23 2015 10:53AM=-=>

    That’s funny. I actually was looking into this last month, trying to find an optimize for “count” clause to help with the batch results coming in a user defined table. Good idea!

    <=-=May 25 2016 12:25AM=-=>

    Yes it would be useful to have…

    SQlpro supported this idea  · 
  18. 10 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  1 comment  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    SQlpro supported this idea  · 
  19. 11 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    SQlpro supported this idea  · 
  20. 17 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    SQlpro supported this idea  · 
← Previous 1 3

Feedback and Knowledge Base