Maybe.. maybe not.

one of my main big tables (clustered columnstore) is partitioned as well - but each partition has 3 Billion...

Columnstore is good for aggregation SQL's - not for plain retrieval of data but 45 min still looks very bad.

on your case I would be interested in seeing how it...

if you get the files in Excel and convert to CSV then it would be better if you define the format of the dates at that point - assuming the...

You also need to consider licencing costs for MSSQL and they can be very complicated.  From memory the minumum licence is 4 cores and then in multiples of 2...

there is nothing we can say to help you there - all those values are specific to your own AD structure. It can be whatever your admins decided it would...

why don't you try it? should be rather easy for you to set up a test case on your own instead of spending time asking if it is possible.

you even...

to use xp_cmdshell within a SP this is NOT what you need.

regarding the SQL Jobs e.g. using sqlcmd as the step type you are missing one step as per below

on...

• This reply was modified 3 years, 11 months ago by frederico_fonseca.

I would go further than that - using better names that make it clear what each date is

with dates as 
(select DateFromParts(Year(current_timestamp)-IIf(Month(current_timestamp)=1, 6, 5), 1, 1) as...

and have you considered that we are not here to do your work?

We can help with particular errors or some logic questions - but rewriting your code is not something...

order is a reserved word - either  use 2 naming convention (which you should be doing anyway) or enclose in square brackets - or both

you just need to replace that "if(od.amend..." with a "coalesce(od.amend.." and the "date(..." with a "convert(date, ...".. and fix the IN clause to have all values enclosed in single quotes...

my advise is for your company to hire a good SQL Consultant with both code and Data analysis experience to go through your issues and find out what happened and...

you going to replace a PROD DB with a non prod one? how is it that your QA db is correct and your prod is bad? or is it just...

it will have issues with connecting to prior SSIS instances.

for plain SQL database/dba access it should be fine with 2008 - maybe not 2005.

latest versions also have the "debug" option...

what is the database compatibility level?

Assigning a value to a variable as part of the declaration is only possible if the database is a certain level - don't remember which...