I wasn't expecting an "answer" ... My initial question was making sure SQL 2016 uses the available RAM, or if I need to configure it somehow as with earlier versions...

It works from a DOS prompt, but not from a SQL Window, (both just testing)
Both servers have "Homebrew01" in the administrators group.

But I need something to work...

The source server is at our remote hosting facility not on an AD domain.
The target server is local at my office, on AD.

These are all new servers....

I'm trying FTP instead, but stuck on that too.

This is supposed to be a daily job, run automatically from spreadsheets with new data.
SQL should be smart enough by now to look at the destination and at least...

A couple of URLs are 350 characters. The import wizard has a default of 255.
Isn't there some way to tell SQL:

"Hey SQL, just take all the frikkin...

Looks like everything is "NT Services"

So even though I'm running it in Management Studio with my Windows Authentication, it's using the SQL Agent permissions ??

I was just hoping there was an earlier version of Upgrade Adviser that works with older OS... that maybe I missed in my search.

Since people upgrading SQL are likely...

Sorry, I wasn't clear. Our Operating System seems to be just short of compatible with the Upgrade Adviser tool.

I want to run the tool to look for "BreakingChanges" etc ahead...

I have a scheduled job on my SQL 2008 server alert me by email if disk space or % free falls below a threshold. Not sure if powershell is different...