Viewing 15 posts - 31 through 45 (of 82 total)
To all,
Apparently, the import failure had nothing to do with dateformat. Although the error was showing timestamp related, the issue was completely a different one.
The CSV file when copied from...
September 5, 2019 at 9:52 am
Hi Thom,
This is not exactly a duplicate post. The previous one was for t-sql related for another server 2016.
This issue is of SSIS (Integration - import from a CSV).
My login...
September 4, 2019 at 9:23 am
There's a new cardinality estimator in SQL 2016. Force your query to use the old one. See: https://stackoverflow.com/questions/47215135/facing-performance-issues-in-sql-server-2016-after-migration%5B/quote%5D
That worked perfectly fine using the Option Hint directly in...
July 15, 2019 at 2:07 pm
Nova,
The execution Plans do look identical. It's quite a big one, so hard to compare every node. It starts off with Hash match (Union) cost 0% 7 of them in...
July 15, 2019 at 1:41 pm
Thank you. Personally I don't like UNIONs too. But these are user queries/views I have to test on SQL 2016 as we are in process of migration from SQL 2008...
July 3, 2019 at 2:40 pm
Jonathan/Thom,
You both are right actually. We have many scripts with dates in dd/mm/yyyy and yyyy-mm-dd format. Plus we have to change few staff members login to English login instead of...
June 24, 2019 at 2:36 pm
Jonathan,
Is this a change in SQL2016? Because the format yyyy-mm-dd behaves perfectly fine in SQL 2008 R2.
I ran your set of correct/incorrect ones and the output changes to yyyy-dd-mm in...
June 24, 2019 at 12:45 pm
Hello
It's worked somehow.
I processed each Dimension separately, after I changed the Impersonation Info to "domain\username: password".
And then processed the Cube itself.
Why would it not work under " use the credentials...
June 19, 2019 at 3:24 pm
... and the server is Windows 2019
Vinay
June 18, 2019 at 5:15 pm
Jonathan,
That made a "significant difference". The initial "splash" v.18 SQL server management Studio comes instantly and takes few more seconds for the server prompt. It's a little slow on the...
June 4, 2019 at 3:44 pm
Lynn,
Spot on. that's exactly what I was after. I was trying with CTEs too, but you won the race.
Many thanks for this.
Bij
April 16, 2019 at 4:42 pm
Hi Drew,
I wasn't very clear with my question, sorry about that.
What I am after is for the below standard stuff using a table, I now want to...
March 7, 2019 at 9:19 am
Steve,
Apologies for the delay in replying. Wasn't actively testing this for sometime.
Basically all the old SSIS packages were created in VS 2008. They all work fine on SQL...
January 10, 2019 at 10:00 am
Thom,
Thank you.
We are upgrading to SQL-2016 by Jan. So, this is the last of 2008R2.
So far it's never given any trouble with "millions" of records.
November 2, 2018 at 10:29 am
Yes, actually it is SQL server 2000 (80) compatibility level.
Is that the reason for this failure?
Btw, I tried with dbo.consent_by_contact too, but wouldn't work.
Vinay
November 2, 2018 at 9:45 am
Viewing 15 posts - 31 through 45 (of 82 total)