You're on 2016. Use the Query Store. Nice and easy way to gather that information. Otherwise, some of the suggestions are good, query the cache, use extended events and...

I'm not aware of a way to do this, no. You can have a query window showing logins. You can refresh that regularly. Or, maybe you're thinking of the Activity...

Good luck. I don't blame you. A friend worked for one when I was growing up. They always got to go to cool places. I just searched for "sql server"...

Quick web search. Yes.

Oh, and doggone it, database settings. ANSI settings especially, but all the rest too. Differences there can lead to different performance characteristics.

First, and I can't emphasize this enough, double, triple, quadruple check that yes, really, these servers are the same. Frequently they are not.

Then, of course, the next question is, are...

When you jump the SQL Server 2014 gap (because no one should ever upgrade to 2014), you do need to be aware of something really important. In SQL Server 2014,...

If you're just getting going, now is a great time to completely ignore trace and trace events and concentrate only on Extended Events. Instead of default trace, look to the...

p.s.  I'm not 100% sure but I don't believe they've disabled the ability to turn ANSI NULLs off yet in 2017.  It has been an advisory for many years,...

So this should be fine? select a.*, b.full_name from alt_id_view a left outer join all_clients_view b on a.people_id = b.people_id It's only bringing in the matched so it could...

I'm seeing an Unfollow link. I just followed you. Below your name, it says Unfollow on the left:

Does that work?

In other news, what do you do when 2 CLI languages for your OS's isn't enough: Introduce a third: https://devblogs.microsoft.com/commandline/introducing-windows-terminal/ I admit I haven't read too far into it,...

I didn't see the need to add a comment. The other answer is shown as accepted with multiple positive votes. The bad answer has now 2 negative votes...

Sounds like you're not logging in correctly to Azure then. You can only use Azure Active Directory, not the regular kind, or, a SQL login, which you say you don't...

Connections should be exactly the same. What's the error?