if you are using a SSIS package and have correctly defined the input file then it will work well with the sample you posted - but if not defined correctly...

look at the rsconfig utility https://docs.microsoft.com/en-us/sql/reporting-services/tools/rsconfig-utility-ssrs?view=sql-server-ver15

regarding your SQL Service accounts - you should be using MSA/GMSA where possible (e.g. as the user that the services run under) so you don't...

and what is the error you getting?

if your VMs are with VMWARE Esx then yes it does apply - and for it to work the following must be enabled

• Server Bios - enable max power
• VM...

or instead of using a file defined within SSIS you create and write to the file using a c# script component as a data transformation within your dataflow.

there you can...

unfortunately and as I said the only way to use it outside SSDT is to have it fully licensed - see https://docs.microsoft.com/en-us/sql/integration-services/integration-services-features-supported-by-the-editions-of-sql-server?view=sql-server-ver15

depending on what you are trying to do you...

and be careful with doing it that way. SSIS is a licensed feature of SQL Server so any PC that executes it will require a full license of SQL Server.

SSIS...

using just min/max/avg will not help much if you have stragglers - you are better off ranking then on durations and then look at the specific ones that are on...

Does not matter what possible options we give you to process from the queue - unless you tells with great detail what you are doing with each row on the...

MAX Server memory should never be left at the default - with 128 GB ram and with SSIS running on same server I would give SQL a max of 100-110...

• This reply was modified 4 years, 2 months ago by frederico_fonseca.

Since SSIS is not SQL - it isn't the same - and the code is not processed as SQL code. Since the data is in the file -...

PowerBI will cache - but if using direct query it will also push the query down to SQL Server - and in this case it will shine if doing aggregations...

that's a basic OR statement -

and (invoiceamount = @amount or @amount is null)

powershell has a quirk - exit status is not the one of the last command executed - been bitten by this a few times.

whatever you do within your scripts you...

no need for further variables.

just do the conversion in sql

delete from T1 where date_cr between convert(int, ?)  and convert(int, ?)