SQL Server

Microsoft SQL Server 2017 powers your entire data estate by supporting structured and unstructured data sources. It builds on previous versions of SQL Server, which have been industry leading for four years in a row and a leader in TPC-E. It scales to petabytes of data and allows customers to process big data through PolyBase using T-SQL over any data. SQL Server has also been the least vulnerable database during the last seven years. SQL Server 2017 brings data insights with business intelligence capabilities that provide analytics at a fraction of the cost on any device along with advanced analytics with support for R and Python.

More details about SQL Server are available in the SQL Server documentation.
If you have a technical issue, please open a post on the developer forums through Stack Overflow or MSDN.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. DCR - Attach database with NORECOVERY

    might be a small one, but a very important one at least for me... Consider you want to move a database that is on a SAN to a different machine, or even move a file to a different disk. The way to do it (or at least one way...) would be to detach and attach. Easy... Unless... you want to do this on a mirror or a Logship Destination...
    Why? Because sp_attach_db always recovers the DB, and for a mirror or logship destination you would need the DB back in NORECOVERY mode.
    So I really need to see a way…

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 20

    <=-=Sep 27 2010 9:57AM=-=>

    Greetings.
    Thanks for your suggestion. This is on my list of enhancements which I’d like to get into the product.
    We will continue tracking this request and hope to get it in as time and resources permit.

    Kevin Farlee
    SQL Server Storage Engine PM

  2. QUALIFY - Request for a New Filtering Clause

    This entry describes a request for a new query filtering clause called QUALIFY in SQL Server.

    As of SQL Server 2008 (including R2) T-SQL supports three standard filtering clauses based on predicates (ON, WHERE, HAVING), and one nonstandard filtering option based on a number/percent of rows and ordering (TOP). Window calculations (e.g., ranking and aggregate calculations that use the OVER clause, and hopefully others in the future) are only allowed in the SELECT and ORDER BY clauses of a query, and therefore you cannot refer to those directly in the filtering clauses that are based on predicates. For example, the…

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  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…
  3. Don't list databases unless current user has permission to access them

    Currently, when accessing SQL server 2008 using the Management Studio and expanding the dabase list, all databases are listed, even though the current user does not have permission to see most of them.

    This also has the effect of not listing anything if one does not remove the additional columns from the "explorer details" window, if the user does not have permission to a database.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  4. Add support for autonomous transactions

    Support for autonomous transactions (i.e. the ability to nest a unit of work) would allow for more concurrency. At the moment an operation that is logically independent such as a logging operation can lock resources until the transaction as a whole succeeds.

    A great example of where this would be useful is in the implementation of sequences. Once a sequence range is allocated the change can be committed independent of the surrounding transaction. Doing so allows other transactions to allocate sequence ranges while the first transaction is progressing. This allows for greater concurrency.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 102

    <=-=Dec 11 2007 2:24PM=-=>

    Hello Anthony

    Thanks for your feedback and feature request. Autonomous transactions are a powerful feature and can be used to satisfy a variety of core requirements, such as sequence generation, error logging, and more. Though autonomous transactions will not be available in SQL Server 2008, we are actively tracking this as a feature request and are considering supporting it in a future release of SQL Server.

    Thank you

    SQL Server Engine Team

    <=-=Aug 31 2008 6:14AM=-=>

    Also consider the ability to pick multiple “atonomous” transactions to simultaneously COMMIT or ROLLBACK.

    For example,
    BEGIN TRANSACTION A
    BEGIN TRANSACTION B
    BEGIN TRANSACTION C
    COMMIT TRANSACTION B,C
    BEGIN TRANSACTION D
    ROLLBACK TRANSACTION A,D

    Here is the kicker: the COMMIT or ROLLBACK is atomic with respect to all named transactions that are listed.

    <=-=Oct 20 2011 11:37AM=-=>

    Competition was and still is so much always ahead:
    Sequences,…

  5. No error raised when a remote procedure times out

    If you call a stored procedure in a linked server, and the provider times out, for
    instance there is a blocking situation on the remote server, SQL Server only prints
    a message, but error is raised, so the condition cannot be caught in BEGIN TRY.

    The problem appears both in SQL 2005 and SQL 2008.

    As indicated in the repro, there is a workaround by looking at the return code
    from the procedure.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 19

    <=-=Apr 8 2008 1:06PM=-=>

    You have closed the bug gy design without a comment. Please understand that this about the most efficient way to insult a customer. May the customer has got it all wrong, but at least he deserves an explanation.

    So could you please care to explain the “design” for this behaviour? What I failed to mention in my bug report, is that if I run the SELECT statement directly against
    the linked server:

    SELECT * FROM REMOTESVR.Northwind.dbo.Orders WHERE OrderID = 11000

    you do get an error raised. So why is no error raised when a remote procedure call times out? It is not considered an error?

    <=-=Apr 9 2008 11:38AM=-=>

    Erland,

    Sorry for not responding sooner. This just was bad timing on our part. Dev and test closed the report before I had a chance to communicate with you.

    The fact that you can�t…

  6. Allow text to be justify aligned in a report

    Text can only be aligned left, center or right. There is no option to justify align text.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 91

    <=-=Apr 17 2009 11:15AM=-=>

    I am currently slated to release a reporting system for a financial industry client that utilizes all Microsoft technology: SQL Server 2008, SQL Server Integration Services, SQL Server Reporting Services. The final proof was rejected by upper management due to the inability to fully justify text. It’s hard to explain to them that this is not available, when it’s considered a technology that Microsoft has been providing (Word, Excel, PowerPoint, etc…) for decades. In the financial industry, fully justified text is considered industry standard and I understand their position.

    Currently the only solution I can offer them is to abandon Reporting Services and switch to Crystal Reports.

    <=-=Jun 18 2009 12:08AM=-=>

    I also need even justification of text on both left and right edges of paragraphs.

    My client needs this for financial publishing of their mutual fund marketing documents, whch are about 50% statistics…

  7. SMSS missing format document

    In the development team I am working to, we are using a formatting code convention different from that used in the book onlines, so when we use the Query Designer, we have to manually format the code. Apart from that, there is not an easy way to format the T-SQL code in any kind of code convention, I mean, differently that in VS for c#, I can't find any "Format Document" or "Format Selection" command (even in VS 2005 itself, there is no way to format T-SQL code)

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 5

    <=-=Mar 28 2006 4:52PM=-=>

    Thank you for your suggestion for formatting t-sql statements. We will consider this for a future release of SQL Server

    <=-=May 12 2011 1:27AM=-=>

    Hi,

    We took a look at this bug along with several others recently. Unfortunately, triaging it against other critical bugs, I do not think we would get to investigating this in the near future. However, we have taken note of this internally, and when we revisit this functionality in the future, we will try and get this resolved.

    Thanks for writing to Microsoft.

    Thanks,
    Chandraveer

  8. Choosing columns for display in Table Designer

    Currently in table designer the available columns for creating tables are Column Name, Data Type, and Allow Nulls. It would be much easier to have certain columns such as Allow Nulls, Identity Column, Seed, and Increment also on those columns, as it would make my table development time faster.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 3

    <=-=Mar 31 2006 8:20AM=-=>

    Quick update. We are placing this bug report under consideration for SP2.

    <=-=Apr 19 2006 11:32AM=-=>

    Thank you for your feedback – we will consider this for a futre release of SQL Server.

    <=-=May 12 2011 4:07AM=-=>

    Hi Derreck,

    We took a look at this bug along with several others recently. Unfortunately, triaging it against other critical bugs, I do not think we would get to investigating this in the near future. However, we have taken note of this internally, and when we revisit this functionality in the future, we will try and get this resolved.

    Thanks for writing in to Microsoft.

    Regards,
    Kamal

  9. Add CREATE DOMAIN command

    Can't define domains in SQL Server 2005 for data types.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 36

    <=-=Feb 17 2006 2:04PM=-=>

    Thanks for the feedback. We’ll consider your input for planning of future release of SQL Server.

    <=-=Jul 19 2007 1:38AM=-=>

    Hello

    please consider ALTER DOMAIN, too.
    This should allow minor changes to the domain (like changing the size of a char column) WITHOUT data loss.

    Thx
    EH

    <=-=Nov 15 2008 7:21AM=-=>

    This feature is a standard feature in ISO SQL and is well used in case tool like Power AMC while modeling the datas. Its a feature that can optimize the data model by fixing globally the types of informations across the tables that will result of no implicit cast while using two columns in a join wich can have been differently created in two different tables. Example : column name in table customer as varchar(25) and column name in table employee as nchar(32). This would be avoided by using a NAME SQL

  10. Module-level table expressions

    There are some situations where you perform a lot of operations on a very
    well-defined subset of a table in an SQL module. A typical case is a process-
    keyed table. That is a table that is keyed by @@spid or some other process
    key. see http://www.sommarskog.se/share_data.html#prockeyed for a longer
    discussion. If you have a procedure that operates on such table, the
    procedure may have a bunch of:

    SELECT/UPDATE/DELETE ... WHERE processkey = @processkey

    This is somewhat error-prone. If the procedure has 20 such operations,
    you may fail to observe that the condition on processkey is missing in
    one of…

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 50

    <=-=May 9 2008 7:48PM=-=>

    I browsed the SQL-2003 standard to see if there was something like this, and nothing jumped out. That makes me suspect there’s a good reason. In some respects, this feature could be like Dynamic SQL, only worse.

    Macro-like abilities are very handy, but they can also be tricky to implement and define. Perhaps you would learn to use the feature effectively, but the parser/preprocessor/optimizer would have to handle whatever this feature allowed, and the results might be surprising. For example (and I think there are many examples), suppose you began a long procedure with

    declare @sessionRows query as select T.id, T.c from T where T.spid = @@spid;

    If @sessionRows is expanded before query execution, these two seemingly-identical statements are completely different:

    — Expression A
    with T1 as (
    select spid, id, c
    from Nisse
    where status = ‘Censored’
    )
    update Trades set…

  11. Mutiple aggregates in PIVOT

    Currently the PIVOT operator is:

    PIVOT ( aggregate_function ( value_column )
    FOR pivot_column IN ( <column_list> )
    [ AS ] table_alias

    I would like to see this enhanced to:

    PIVOT ( aggregate_function ( value_column ) [ ,...n ]
    FOR pivot_column IN ( <column_list> )
    [ AS ] table_alias [ ( column_alias [ ,...n ] ) ]

    The resulting columns are ordered such that all of the aggregation function applications for a single pivot column value are consecutive.

    This would permit both multiple aggregation functions on a single value column (e.g. both MIN and MAX) or application of aggregation functions on…

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 12

    <=-=Nov 13 2006 6:46PM=-=>

    Thank you for submitting this feature request. This is now under consideration for upcoming version of SQL Server.

    —G2

    <=-=Mar 10 2011 6:15PM=-=>

    Hello Mark,

    I have resolved your request as duplicate of one below:

    http://connect.microsoft.com/SQLServer/feedback/details/127071

    We will track your feature request as part of that one.


    Umachandar, SQL Programmability Team

    <=-=Mar 10 2011 11:49PM=-=>

    I do not agree that this request is a duplicate of feedback 127071. That feedback is for a dynamic column list (dynamic IN) , where the internal query determines the shape of the output result set. This query is to support multiple aggregates; the shape of the output result set remains static. Specifically I am not suggesting any change in the IN () clause, which is the target of 127071.

    A concrete examples that we have face is when dealing with currencies – we need to simultanously aggregate…

  12. Enable SQL Developer Edition to target specific SQL version

    When developing using SQL Developer Edition (SSRE, SSIS, SSAS, SSRS), it is possible to use enterprise features (eg: Partitioning). However, if the solution needs to be deployed to a customer with SQL Standard Edition, developers usually find out after the fact that the particular feature used is not supported by the destination Edition.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 186

    <=-=Oct 7 2009 7:03AM=-=>

    I think it could be even deeper down, because not everybody develops using BIDS or Visual Studio or the UI. If I run an Enterprise-only statement in a query window, I should be able to see an attention event, or something similar to the deprecation warning, when using features that don’t run on the target you’ve specified. When I know I am targeting standard or lower, I can simply check for that event. Much simpler than reviewing all of the features and code against some checklist. This could be set at the database level and/or server level, so that you can be working on multiple dev databases at the same time, potentially with one targeting express and one targeting standard… then an event would be raised if, for example, you used CREATE PARTITION SCHEME. But you’d also want to catch server-level things (e.g. …

  13. Placing Database under Source Control

    I have been trying to evaluate how SQL Server Management Studio integrates with source control. The only thing I can find is the ability to place a database 'solution' under source control and that basically puts create scripts and change scripts under source control. It doesn't keep 2 or more people from making changes to the same object.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 2

    <=-=Jun 20 2008 2:27PM=-=> harolds,

    Thank you for the suggestion. I will send a notification to the feature team to keep tracking of this suggestion.

    Regards,
    Eric Kang
    Program Manager, Microsoft SQL Server

    <=-=Aug 22 2008 11:49AM=-=>

    Harold is a colleague of mine. It just seems strange to us that all SQL related source control is done at a SQL script level instead of an actual object level within SQL Server itself. You should be required “check-out” a stored procedure, for example, before you can ALTER it. If you “Undo check-out” then the object should be restored to it’s previous state.

  14. Support ISO 9075 standard string concatenation - double pipe

    The ISO SQL standard 9075, feature ID E021-07 covers string concatenation. The standard specifies this is a double pipe character sequence ('||'). SQL Server doesn't currently uphold this standard.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 54

    <=-=Dec 13 2007 3:41PM=-=>

    Thanks for the feedback and the many votes. Note that while we do not use the standard syntax for it, we are providing equivalent functionality with the ‘+’ operator.

    Nevertheless, we will look into it for a future release.

    Best regards
    Michael

    <=-=Dec 13 2007 4:26PM=-=>

    Thank you, Michael.

    While I am familiar with the “+” operator for string concatenation, it is both non-standard, making writing SQL for SQL Server more burdensome, and overloaded, causing hard-to-find type-casting errors.

    The double-pipe would be a great improvement in a number of scenarios. I appreciate your consideration of it for a future version.

    <=-=May 1 2008 6:50AM=-=>

    This is needed so that one version of a SQL statements can be ported to different database platforms without change.

  15. Allow literals and read only table data to be represented as enums

    It would be really useful to represent system values to be used in code as constants rather than having to hard code integer values.

    This means that lookup tables can use nice tinyints as the surrogate PKs but when referenced in code the code can use the textual representation.

    Essentially data driven enums.

    I am happy for the restriction that this only applies to read only data.

    an example where this wouldbe useful is the system message types/contracts in service broker. Currently you have to have strings like 'http://schemas.Microsoft.com/SQL/ServiceBroker/DialogTimer'; in your code. which means you are comparing against…

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 236

    <=-=Jan 29 2007 11:51AM=-=>

    Thanks for the feedback. There are a few alternatives to enable this, we’ll consider it for future release.

    - Christian Kleinerman

    <=-=Aug 9 2007 10:55AM=-=>

    Ageed, this would make dev work much simpler, not to mention maintaining the system afterwards.

    <=-=Aug 27 2007 9:05PM=-=>

    I agree with the call for enums, but I do not believe it should be implemented as a secondary lookup table table, or at least, the lookup table should be handled by the system, and should not require the developer or DBA to create it up front.. I think any implementation should be functionally equivalent to the MySQL column data type. It works and is widely adopted in the MySQL crowd, and would provide better portability to/from other systems.

    <=-=Aug 27 2007 9:35PM=-=>

    Some type of Enum capability would certainly make development much easier. Having such a feature may also…

  16. Multi-column subreports do not work

    I'm trying to import several critical reports from MS Access. The Access reports display subreports that are defined as multi-column. The parent report displays such a subreport in a fixed-height subreport control, thus causing the subreport data to flow into multiple columns within the subreport rectangle.

    What happens in SSRS is that the subreport rectangle grows vertically, and all the subreport rows appear as one column.

    The rendering of the Access subreport cannot be reproduced in SSRS, thus I cannot offer these reports to the company via the report server.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 29

    <=-=Sep 24 2008 12:10PM=-=>

    Hi, I’ve the same problem and not found solution in all the web, it would want that they fixed that problem because I need that report for a statement of account for a company in ssrs.

    I’d really appreciate any ideas you might have.

    Note: Sorrry for my english.

    <=-=Sep 30 2008 6:55PM=-=>

    Hello,

    Thanks for writing in about this. It sounds like you’re asking for sort of a “snaking” subreport that fills horizontally after it reaches its vertical limits. SSRS does not currently support such a construct and I’m not aware of any workarounds for this.

    I have converted this filing to a feature request and have marked it to be reconsidered as we begin our next round of planning. As such, I will leave this issue active. I encourage the MS Connect community to vote on this request if they have a…

  17. Make Latin1_General_(100)_CI_AS the default collation for US English

    This description is identical with:
    https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=357973

    When installing SQL Server you need to select a server collation. However, Setup permits you to go with a default. This may seem convenient, but it often backlashes, because the default is unsuitable for a number of reasons.

    A real-world case: I was contacted by a guy who was fearing for his job, if he could not get some speed out of his database. The query he show me was a simple lookup the PK. The problem was that the application (using Java in Websphere) worked with Unicode, but the table had varchar keys.…

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 10

    <=-=Aug 6 2008 10:15AM=-=>

    Hello,

    Thank you for sharing your ideas. As you say this one is somewhat less revolutionary than not having a default collation at all; you’re also right that the major obstacle in doing it is a back-compat. That being said the idea is still being discussed. I will keep you informed on the results of the discussion.

    Thanks,
    Krzysztof Kozielczyk

    <=-=Aug 6 2008 12:07PM=-=>

    I would be intrigued to know, what exactly is this backwards compatibility issue about? The only I can think of is existing scripts for unattended install, but I would expect such scripts to require modifications for new versions of SQL Server anyway. Is there something I have overlooked. I would appreaciate if you could details this, either here, or via private note over email.

    <=-=Mar 17 2011 11:24AM=-=>

    Hello Erland,

    Thank you for submitting this suggestion, but we’re trying to…

  18. Allow enabling and disabling of a column's IDENTITY property

    Sometimes IDENTITY columns need to be cleaned up a bit -- their values updated or re-ordered, for instance. This can occur when data replication strategies fail, or when unexpected data was inserted. This is a somewhat rare occurrence, but when it does happen it can be extremely painful due to the fact that IDENTITY columns cannot be updated, and the property cannot be enabled or disabled. As a result, in most cases doing what should be a simple update requires creation of a new table.

    Likewise, we sometimes want to be able to turn an existing column into an IDENTITY…

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 60

    <=-=Jan 18 2007 10:51AM=-=>

    Thank you for the feedback, we’ll look into ways to improve on the scenario you describe.

    Thanks,

    - Christian Kleinerman

    <=-=Jul 5 2007 12:27AM=-=>

    IDENTITY columns CAN be updated! See workaround…

    <=-=Feb 21 2008 8:08AM=-=>

    Workaround doesn’t work in 2000 or 2005.

    I would rate updates more important than turn on/off, but both would be very handy.

    <=-=Oct 16 2009 4:00AM=-=>

    @way0utwest – the workaround definitely does work in 2005 – I used it just the other day!

    <=-=Feb 4 2010 5:16PM=-=>

    I have added a partial workaround using ALTER TABLESWITCH.
    I do agree that this would be a useful extension to ALTER TABLE ALTER COLUMN though…

    <=-=May 2 2013 8:10PM=-=>

    I just realised how painful having identity columns !! we recently wanted to merge two client databases (their businesses merging) and it became a nightmare!! Because we used identities as…

  19. Attach with NoRecovery

    For VLDB and Highly Available users with SAN copy infrastructure, the ability to attach a database with NORECOVERY to use as a log shipping target would be a big benefit. This would leverage the SAN copy with the SQL attach capability to quickly initialize log shipping partners.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 13

    <=-=Apr 18 2007 9:54AM=-=>

    Thank you for your suggestion.
    This is functionality which we are actively investigating, but cannot commit to at this point.
    I will keep you informed as the situation develops.

    <=-=May 14 2007 10:18AM=-=>

    This suggestion is being closed as a duplicate of another suggestion for the same functionality. Rest assured that the idea is not rejected, we’re just consolidating the work items in our database to make tracking more manageable.

    <=-=May 14 2007 10:19AM=-=>

    Closing as duplicate as previously discussed

    <=-=May 14 2007 10:20AM=-=>

    Item being closed as previously discussed.

    <=-=Jun 14 2007 10:06AM=-=>

    What is the duplicate suggestion this was consolidated into? I want to add that to my watch list.

    <=-=Feb 4 2009 8:16AM=-=>

    Typically the SAN vendors utilize the VDI API layer to coordinate these external backups with SQL Server (BACKUP DB WITH SNAPSHOT…). This creates a header (.bak)…

  20. triggers before insert and row level.

    Need to have real Before triggers and row level triggers. SQL doesn't have these triggers or sequences. They have "instead of" but not a real Before Trigger like enterprise level databases have. It's a real pain to program in SQL or to convert from Oracle or MySQL.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 43

    <=-=Jul 3 2007 12:12AM=-=>

    BEFORE triggers are part of ANS SQL 99 (and 2003), and as such have been implemented by many manufacturers (Oracle, IBM).

    It’s time MS implemented ANS SQL.

    <=-=Jul 8 2007 5:49AM=-=>

    That request is for 3 features instead of one!
    1) I agree about Before Triggers
    2) Row triggers are easily done with SQL although with non ANSI syntax. But they are a bad practice, so low priority for me.
    3) Sequence would be nice eventually, but it is not a show stopper.

    <=-=Aug 13 2007 2:53PM=-=>

    Thank you for posting your request. We realize that BEFORE triggers are extremely useful, specifically in migration scenarios. Unfortunately, we are not able to provide this functionality in SQL Server 2008. We are considering it for a future release. Meanwhile, we suggest using INSTEAD OF triggers to achieve similar functionality.

    <=-=Aug 17 2007 1:01PM=-=>

    INSTEAD

  • Don't see your idea?

SQL Server

Categories

Feedback and Knowledge Base