Thanks, I tried again, this time I did get MSOLEDBSQL.1; in the connection string.

I wonder how I got SQLOLEDB.1 in early operation, I remember I chose the same one.

Thanks all

Thanks. Yes it works. But if I look at the connection string: it is like I posted earlier:

Data Source=myserver;Initial Catalog=Truancy;Provider=SQLOLEDB.1;Integrated Security=SSPI;Application Name=SSIS-2019SSIS-{9CDABED8-B895-4E1F-86F9-1BE15149E31F}mserver.mydb;Auto Translate=False;

It is SQLOLEDB not MSOLEDB.

And microsoft online doc...

I did google before I posted and found the page too.

But that is not the answer. Microsoft said those two are deprecated, new development should use the new one. But...

Thank you, but when I tried to add a connection manager, in the provider list, I don't see there is a MSOLEDSQL. I do see one named microsoft OLEDB provider...

Thank you. We have the two situations you mentioned.

First if export then import , when doing import from the Ispac, will that automatically upgraded it to 2019 SSIS?

second, if deploy...

Another  place  I saw similar of this is in a sql script:

select cast(stu.VisibleID as int) as StudentID

,case when r.VisibleRouteID like '[0-9][0-9][0-9][0-9]-T%' then trex.OriginPointID

when r.VisibleRouteID like '[0-9][0-9][0-9][0-9]-I%' then trex.OriginPointID

when r.VisibleRouteID like...

Thank you, just saw that  too. I did unintall CU7, and apply CU6.  For now I think we are fine.

We will have to find another maitenance time for next CU8...

Thanks for the article.

Question, 1. how can you know the applilcation is using kerberos? In my environment, I always use domain account instead of local system account for the SQL...

This is more context of the script code:

Public Overrides Sub PreExecute()

'Sample valid value:

'Eff 20070905 Rev 00

'Pattern should match Route Number in VisibleRouteID string, allowing for a few minor formatting errors...

Thanks, I also heard complex logic should handle in business layer not on database layer. Is that just some people's preference?

Thanks all for the analysis and tips!

There are SSIS packages for other purpose of this project, but not for this process.

• This reply was modified 6 years, 2 months ago by sqlfriend.

Yes, there was a very experienced SQL developer contractor too.  He designed the whole database model, build up the database, create stored procedures and created some SSIS packages.

Thanks much, it makes sense to me.

The project was a big one and a complicated one. And an entire project team with several good developers and BA and Project manager...

Thanks. This overnight update process is a part of  a  big project we had and hired several contract developers and project team. The web service/applications does very complicated process for...