Anonymous

My feedback

  1. 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 » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  2. 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 →
    Anonymous supported this idea  · 
  3. 6 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 » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  4. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  5. 147 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    Upvotes: 3

    <=-=Jan 8 2018 12:16PM=-=>

    Thanks for the suggestion.
    We’ll consider it for a future release.

    Are there specific limitations imposed when you have the filegroup, e.g., no database snapshot, that hold you back from creating the filegroup?
    Or is it only the feeling of not being able to turn back?


    Jos de Bruijn – Database Systems PM

    Anonymous supported this idea  · 
  6. 1,014 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  399 comments  ·  SQL Server  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Anonymous commented  · 

    This needs to be added back to SSMS. Please Microsoft if you care about your SQL Server developers, please restore it.

    An error occurred while saving the comment
    Anonymous commented  · 

    Please bring back the debugger. Microsoft tools have had built-in debugging facilities from the release of QBASIC back in about 1990.

    Anonymous supported this idea  · 
  7. 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 →
    Anonymous supported this idea  · 
  8. 303 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    60 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  9. 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: 33

    <=-=Aug 24 2006 2:42PM=-=>

    Thanks for the feedback. We are looking into providing such functionality for one of the upcoming releases.

    <=-=Nov 3 2006 4:13PM=-=>

    I second his opinion, forcing xpaths to be literal is far too restrictive. At least allow them to be generated strings (as it is now they must be string literals).

    <=-=Jun 4 2007 1:49PM=-=>

    This is def. important to be able to shred the XML without using dynamic SQL and exposing the code to threats.

    <=-=Mar 4 2008 8:25AM=-=>

    I concur. This would be of tremendous benefit as I have similar XML documents with different namespaces as an inheritance tree and have struggled to get a workaround.

    <=-=Feb 25 2009 11:48AM=-=>

    This is a no brainer in my book. It needs to be done, end of story. Dynamic sql is a pain to work with and shouldn’t be the recommended way

    <=-=Jul 26…
    Anonymous supported this idea  · 
  10. 6 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: 39

    <=-=Dec 3 2008 4:28PM=-=>

    Thanks for the feedback. The following shows how we would have to approach this.

    The nodes() method returns N rows one for each node selected by the expression inside the nodes() method. Each of that node is being set as the context item for the expressions inside the value/query/exist/nodes methods. The definition of the position() function is

    http://www.w3.org/TR/2007/REC-xpath-functions-20070123/#func-position

    16.1 fn:position
    fn:position() as xs:integer
    Summary: Returns the context position from the dynamic context.

    where context position is defined as:

    [Definition: The context position is the position of the context item within the sequence of items currently being processed.] It changes whenever the context item changes. When the focus is defined, the value of the context position is an integer greater than zero. The context position is returned by the expression fn:position(). When an expression E1/E2 or E1[E2] is evaluated, the context position in the inner…

    Anonymous supported this idea  · 
  11. 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: 4

    <=-=Oct 9 2007 4:42PM=-=>

    Dear Mike

    Thanks for your feedback and suggestion. Due to the fact that we are close to finalizing our SQL Server 2008 release and the relative prioritization of this functionality, we will be looking into adding XQuery function support in a future release of SQL Server.

    Note that for simple expressions, you can now use the let clause in SQL Server 2008.

    Best regards
    Michael

    Anonymous supported this idea  · 
  12. 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 » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  13. 5 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 →
    Anonymous supported this idea  · 
  14. 442 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    14 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  15. 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 » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  16. 6 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 →
    Anonymous supported this idea  · 
  17. 15 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 →
    Anonymous supported this idea  · 
  18. 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 →

    Upvotes: 5

    <=-=Mar 24 2011 4:01PM=-=>

    Hi,

    Thank you for reporting the issue. We will go over the repro steps, investigate the issue and update you when we have further information.

    Thanks & Regards,
    Pooja Harjani
    Program Manager

    <=-=Jul 14 2011 10:05AM=-=>

    We are having the exact same issue, we are using the 64 bit driver on a 64 bit server. We can write to the local hard drive just fine, but not a UNC path.

    Is there a resolution for this?

    <=-=Apr 4 2012 10:12AM=-=>

    Confirmed still an issue. This is with the version 14 of the ACE.OLEDB that registers itself as version 12 (why is THAT still a bug by the way).

    Come on now MS, this is important stuff especially with the push for 64-bit. A year later and there is no update?!

    <=-=Apr 4 2012 10:19AM=-=>

    This is more of an edit to my…

    Anonymous supported this idea  · 
  19. 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 » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 5

    <=-=Mar 13 2008 4:54PM=-=>

    Thank you very much for taking the time to post your feedback. I am sending this issue on to the right person to evaluate your request and respond with more feedback.

    <=-=Mar 14 2008 2:25PM=-=>

    Dear Jacob… thanks for filing this request. We indeed see the need for such functionality and your request helps us in prioritization. Can you please add your rating?

    We have one technical solution based on the new hierarchyID that we are looking into (not this release though given the timeline).

    Current workarounds for your problems are recursive SQL user-defined functions, or applying an XSLT style sheet.

    Best regards
    Michael

    Anonymous supported this idea  · 
  20. 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 →
    Anonymous supported this idea  · 
← Previous 1 3 4

Feedback and Knowledge Base