{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 可以哭但决不认输i 的问题《known and “unknown” incompatibilities between sql》','https://www.manongdao.com/q-997879.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
as usual, we'd like to think that there won't be any trouble migrating our applications to the latest sql version...
but...
but...
but...
well, just to be prepared, has anybody stumbled into some nasty incompatibility issue?
(for example, I remeber that after migrating from 2000 to 2005, one linked server we had to a sql 6.5 server stopped working)
The msdn list of deprecated features is very comprehensive.
The MSDN article Backward Compatibility for SQL Server 2008 covers all of the major components.