I believe your only solution for this is to setup a SQL Agent job that executes the SSIS package (with a defined proxy) and introduce a SP to allow your...

what will that package do?

• Access file system (on another server or locally to the server - if remote it won't work)
• access remote database (if so it will require...

what is that proc doing?

and what are you trying to accomplish (end target)

as it resides on SSISDB I would suspect you are trying to start a package execution - and...

@databases = 'USER_DATABASES,db1,db2', -- USER_DATABASES will do all user db's including db1 and db2 - if your intention is to backup only db1 and db2 then your strings should be

@databases...

as you have been advised on other similar queries you need to implement a storage of these metrics onto a table at a point in time - and then build...

you need to dig through all tables, views and functions that query uses.

it is highly possible that one of them has a filter on the users (common for MS CRM...

while the package is running its normal that the row counts is different - writing to a file is a lot faster than loading to a remote oracle database.

counts that...

Oh, I get...

thanks for replies - does clarify things a lot.

regarding the particular test

insert into newtable with (tablock) select * from old table where $partition.<partitionfunctionname>(<partitioncolumn>) = <partitionnumber>

where partitionnumber = one of the...

I didn't give more details just to allow others to try and...

How busy is that server?

for that spec the inserts into new table should not take 1 hour for a pitiful 12 million rows unless server is nearly maxed.

regarding table

- are...

But that doesn't have anything to do with how many drives you have or whether or not you mix MDFs with LDFs.  It only has to do with the...

Cloud is slightly different than on prem - while on prem normally IOPS  and max throughput are not limited on a per vm and/or disk type/size, on cloud that is...

answer is not always correct on this case.

for an azure sqldb its either how many vcores you allocated or how many dtu's depending on the model you chosen.

and how much ram and what are the disk types...