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. Option to defer foreign key constraint checking until transaction commit

    There are various "chicken and egg" scenarios where it would be desirable to defer the checking of referential integrity constraints until commit time on a transaction.

    4 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: 106

    <=-=Apr 20 2006 7:33PM=-=>

    As a further example, consider flushing the contents of an ADO.NET dataset to the database server. Currently, the order of the updates is critical. It would simplify code design if you could just a) start a transaction b) send all the updates c) commit them.

    <=-=Oct 13 2006 1:35PM=-=>

    Hello Greg,

    Thanks for the feedback. We are aware of this and looking into it for a future release.

    Sameer Verkhedkar
    SQL Engine
    [MSFT]

    <=-=Apr 9 2008 5:07AM=-=>

    This is a duplicate of feedback id 124624.

    The SQL ANSI-92 standard is to defer constraint checking until the commit phase – only 16 years ago now.

    It is not a question of performance or faster dev, it is a fundamental to any database to be able to change a record from one consistent state to another consistent state within a transaction,…

  2. Additional Query Hint: OPTION (MATERIALIZE (cte_name,...,n)

    Sometimes queries would perform faster if one or more table expressions were evaluated individually & "materialized", rather than the optimizer/algebrizer transforming the query.

    Providing a query hint which enumerates those CTEs we want materialized would provide a more elegant alternative to temp tables/variables and manually breaking-out the query into steps. Of course, there will be times when a temp table, and appropriate interim indexes, will still be needed. But materializing as a worktable, could improve performance, while keeping the query SQL-esqe. (as opposed to procedural)

    4 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: 17

    <=-=Aug 16 2009 6:38PM=-=>

    Duplicate:

    https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=218968

    <=-=Aug 27 2009 3:30PM=-=>

    Hello Mike,

    Thank you for the feedback and sorry for the delay in responding to you! I’m going to resolve this item as duplicate of the feedback item 218968 (see Adam’s comment). You can also vote on that item to increase its visibility internally.

    Regards,
    Boris Baryshnikov.
    SQL Server Engine

    <=-=Apr 4 2013 4:48PM=-=>

    Please consider the ability to specify the materialized table’s PK with the materialization hint else I’m still out of luck for some cases. I am constantly using temp tables to work around the lack of materialization issue. Thanks!

  3. 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.

    4 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.

  4. 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&#39; in your code. which means you are comparing against…

    4 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…

  5. 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.

    4 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

  6. 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 →
  7. SSRS 2016 - KPI with profile dependencies

    I try since several days to set a KPI for each user.

    In fact, the user must have his number of remaining holidays. To do this, the dataset is filtering with the USERID.

    But, it's not possible to refresh the KPI if the dataset contains a profile dependencies.

    In my case, it is not a report but a KPI. A KPI is present at the connection of the user. The user does not need, as a report, click to launch an execution. So I can not use the user profile to display a KPI.

    One topic is open in the…

    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: 14

    <=-=Sep 8 2016 5:20PM=-=>

    Thanks for your feedback – it is currently not possible to personalize KPI’s in Reporting Services, and this is implementation is by design currently. However, it is something we will consider for a future release based on customer feedback. I will mark this item as closed as by design, but we have this already on the list of features we’ll be considering to add in a future release.

    Thanks,

    The SQL BI Team

    <=-=Feb 25 2017 7:34AM=-=>

    Dear Vivien,

    I’ve tried this as well – I just send the USERID to a Stored Procedure – and couldn’t get it to work – patched and tried everything… I hope it will come soon – its obvious that this is something you want?

    Not that it is smart – but you can create a dataset per user and then a do a KPI for each user…

  8. 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,…

  9. Allow Common Table Expressions in all query expressions

    Currently, a Common Table Expression (CTE) is allowed only in query statements (SELECT, INSERT, UPDATE, and DELETE). According to the SQL:2003 standard, a CTE (or "<with clause>", as the standards call it) should be allowed in all query expression, which includes subqueries. This would enable us to write, for instance:

    IF EXISTS
    (
    WITH tab AS
    (SELECT 1 AS col)
    SELECT * FROM tab
    )
    PRINT 'okiedokie'
    ELSE PRINT 'not ok';

    This syntax, which is allowed according to SQL:2003, is not accepted by SQL Server 2005. I have reported this as a bug (see https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=254336), but this has been…

    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: 47

    <=-=Nov 14 2007 11:20AM=-=>

    Hello,

    Thank you for sending your feedback to us. We will consider adding this functionality in a future release of SQL Server.

    Thanks,
    Vineet Rao

    <=-=Dec 3 2007 1:42PM=-=>

    Dear Hugo

    Thank you for your feedback. I really like your suggestion and I can see how useful it could be. Unfortunately, we’re at a point in the release cycle for SQL Server 2008 where we’re not able to address this issue as part of the release. We’ll consider it for the next release.

    Best regards,
    Eric Hanson

  10. bcp utility should support RFC 4180 CSV files

    The BCP utility (and it's BULK INSERT sibling) represents the fastest way to load bulk data into SQL Server. Unfortunately, it only has the most basic support for delimited files. It's impossible for the delimited file to have the delimiter in any of its field values.

    CSV, a type of delimited file, has a standard way for dealing with special characters in its values, defined in RFC 4180 ( http://www.ietf.org/rfc/rfc4180.txt ). But BCP only supports use of comma as a delimiter; there is no support for the additional features of the CSV file format.

    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: 21

    <=-=Mar 24 2006 10:28AM=-=>

    This is a reasonable suggestion and will will consider it in the future. Could you supply more information why you need this enhancement? You can have commas in values that are quoted. Could you explain why this does not meet your needs?

    <=-=Mar 25 2006 3:23PM=-=>

    It’s a common question on how to load files where some fields are enclosed in quotes, and where there is a header where it is not. Example:

    col1,col2,col3,col4
    12,“This is col2”,“And col3”,19

    This particular file is not loadable by BCP at all. On the other hand:

    col1,col2,col3,col4
    “12”,“This is col2”,“And col3”,19

    this one is, because in the format file you can defined an initial dummy column that will swallow the header.

    I have previously suggested that it should be possible to describe a header, so that BCP can skip it.

    Adding pre-defined support for CSV seems like a…

  11. 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

  12. 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

  13. Associate Stored Procedure Parameter Datatypes with column datatype

    This is a feature that Oracle has with PL/SQL. When creating a stored procedure and defining a parameter, there should be a way to define the datatype of the parameter and associate that with the column of a table. This way when a table column datatype size changes or type changes the stored procedure parameter is automatically changed to reflect the table change.

    This would greatly help during development

    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: 4

    <=-=Jul 21 2009 7:55AM=-=>

    Hi,

    Thankyou for this suggestion. Makes good sense. (Of course, declaring @coldat to be typeof foo.col1 would still allow us to call get_foo with any argument of that type. That’s to say, it does not tie get_foo to work only with the particular column foo.col1)

    (It’s also worth considering that typeof could apply, not just to a single column, but a set of columns)

    Amazing really that such a simple idea (which is time-saving, and avoids spontaneous breakage down-the-line) was not included into the SQL language from the outset.

    Anyhow, I’ll add it into the TODO list.

    Thanks,

    Jim Hogg

    <=-=Aug 18 2009 11:02AM=-=>

    The was a great feature that Informix had almost 10 years ago. You never had to look up the exact column var type from the table. We get bugs all the time from column sizes being increased, but the sproc…

  14. 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. …

  15. 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.

  16. Add ability to disable a tablix in a SSRS report

    During development it is often beneficial to copy and paste a report in order to re-use a layout. In doing so the developer may choose to bind the report's existing tablix objects to new datasets thereby potentially rendering any existing expressions in the tablix as invalid if they refer to dataset fields that do not exist in the dataset to which the tablix is now bound. This then leads to errors being thrown when switching to preview mode.

    It would be a useful aid to development, therefore, if a tablix could be disabled and thereby removed from processing when switching…

    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 →
  17. 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…

  18. 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)…

  19. Defered Constraint Checking

    We often need to reload application tables, such as configuration, enumeration values etc which we do via a bulk insert from application generated export. When foriegn key constraints are added against these tables deleting and reloading data results in constraint violation. Since an alter statement cannot be placed in the same batch the process constraint disable/reenable cannot be performed within the context of the transaction to ensure constraint is reenabled if the data reload fails.

    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: 6

    <=-=Jul 9 2007 12:51PM=-=>

    Dupe of:

    https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=124624

    <=-=Jan 22 2008 2:09PM=-=>

    Kurt,
    Thanks for your valuable feedback and sorry for the late answer. As you might have seen in the community discussion comment of your submission, there is a related suggestion about the same issue. We are planning to implement this feature in our next major release. This other suggestion also includes a possible workaround, see https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=124624
    With best regards,
    Roman

    <=-=Apr 5 2010 3:12PM=-=>

    Hi,
    I have resolved your request as duplciate of feedback item below:

    https://connect.microsoft.com/SQLServer/feedback/details/124728


    Umachandar, SQL Programmability Team

  20. Make SSDT Available for Linux as well

    As of now, if we need to build the SQL Server project, we need the SSDT toolkit on a Windows machine to build the project. Is it possible to make it available for Linux as well so that we can build the SQL server project not only on Windows but on Linux as well?

    2 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 →
  • Don't see your idea?

SQL Server

Categories

Feedback and Knowledge Base