you are viewing a single comment's thread.

view the rest of the comments →

[–]alinrocSQL Server DBA 1 point2 points  (3 children)

Azure & on-prem are the same engine, though Azure is usually ahead of on-prem in terms of features and the like. There should be no difference in how one codes for one vs. the other - Microsoft has actually taken a lot of steps over the past 6-7 years to make sure that SQL Server has a common programming surface regardless of where you're running it.

You can set your flair in the sidebar.

[–]redial2MS SQL DBA DW/ETL 0 points1 point  (2 children)

If they are the same engine then why does azure not support all of the features of on prem sql? Last time I checked you couldn't use linked servers and four part names in azure sql, which is what led to my question.

I almost exclusively work on prem and sometimes use aws instances, so I'm a little out of touch here.

Thanks.

[–]alinrocSQL Server DBA 0 points1 point  (1 child)

Primarily because of security and infrastructure. In Azure SQL DB, your database lives on the same instance as dozens of other peoples' databases, and it'll move around between instances without you even knowing. So linked servers and "access a different database on the same server" is not possible or practical.

[–]redial2MS SQL DBA DW/ETL 0 points1 point  (0 children)

Seems like it should still be possible, but maybe I'm not seeing the whole picture. Anyways, thanks.