SQL Server: Going In Next, Going In Future, Gone With the Wind?

Hey Folks,

You might be wondering about what this title deals with? This title makes you aware of the features which are removed or will be removed in the future while using SQL Server.

So, with the release of every new version of SQL Server, there are some changes, i.e. the feature is being changed or removed and that make no sense with the newer feature set.

Discontinued – It means that a feature were used to work in the previous version but no longer available in SQL Server 2008.

Deprecated – It means the feature still works in SQL Server 2008, but will be going to be removed from the future version.

Here I have highlighted three lists:

Going In Next Version (Deprecated):

Some features which will not be available from the next version, so it’s better that you remove it from your code:

  • Older backup and restore options
  • SQL Server 2000 compatibility level
  • DATABASEPROPERTY command
  • sp_dboption
  • FastFirstRow query hint (use Option(Fast n))
  • ANSI-89 (legacy) outer joins syntax (*=, =*); use ANSI-92 syntax instead
  • Raiserror integer string format
  • Client connectivity using DB-Lib and Embedded SQL for C

Going In Future Version (Deprecated):

Some feature which will not be in use in the future version, so you should try to remove these from your code:

  • SQLOLEDB
  • Timestamp
  • Text, ntext, and image data types
  • Older full-text catalog commands
  • Sp_configure ‘user instances enabled’
  • Sp_lock
  • SQL-DMO
  • Sp_adduser
  • Setuser
  • System tables
  • Group by all

Gone (Discontinued):

Some features that are no longer available in SQL Server 2008 are:

  • SQL Server 6, 6.5, and 7 compatibility levels
  • Surface Area Configuration Tool
  • Notification Services
  • Dump and Load Commands
  • Backup log with No-Log
  • Backup log with truncate_only
  • Backup transaction
  • DBCC Concurrencyviolation
  • Sp_addgroup, sp_changegroup, sp_dropgroup, and sp_helpgroup

Hope you like this post.

 

Regards

Piyush Bajaj

Like us on FaceBook Follow us on Twitter | Join the fastest growing SQL Server group on FaceBook

Follow me on Twitter  |  Follow me on FaceBook

Data Platform Virtual Summit 2020

Subscribe to SQLServerGeeks YouTube channel. If you want more learning content in your inbox, subscribe to SQLServerGeeks Bulletin.

SQLServerGeeks YouTube | SQLServerGeeks Bulletin | SQLServerGeeks Twitter

Avatar

About Piyush Bajaj

I am very passionate about SQL Server. I also did certification on MCSA – SQL Server 2012, Querying and Administering; MCTS – SQL Server 2008, Database Development; and MCTS – SQL Server 2005, Implementation & Maintenance, which helped me to get more knowledge and interest on this field.Please feel free to drop me any question online or offline, I will try to give you the best possible answer from my side.Right now I am working as a SQL Server developer in TCS. I have an experience of just 2.6 years, well I can only say that “If you have an interest and passion, experience might become a very small thing”.

View all posts by Piyush Bajaj →

5 Comments on “SQL Server: Going In Next, Going In Future, Gone With the Wind?”

  1. I am not sure which next version are you talking about but in Denali CTP “Option(Fast n)” and “DATABASEPROPERTY” is still available and I think these two properties are gonna be available for a very very long time…

  2. Hi Sachin. I am ofcourse talking about Denali as it is the next major release.

    So i will try to answer your question one by one-

    1. “Option(Fast n)” – I will again suggest you read my blog CAREFULLY once again, i have told to use Option(Fast n) instead of FastFirstRow query. I have not written that Option(Fast n) will be removed.

    2. “DatabaseProperty” – DENALI has not yet been relased 🙂 still strongly recommended by the Microsoft not to use it in the Coding, instead use “DatabasePropertyEx” and will be removed in NEXT version. It would be better for your knowledge if see this link: http://msdn.microsoft.com/en-us/library/ms176049(v=sql.110).aspx.

    Its said by the Microsoft, you cant deny it… 🙂

Leave a Reply

Your email address will not be published. Required fields are marked *