Viewing 15 posts - 1 through 15 (of 80 total)
I wrote the following (as I realized the data is strictly about pupils up till a certain age):
[note: this will fail when someone will send in stuff like '20-08-25', but...
June 20, 2025 at 4:01 pm
Yes, it is due to a lack of understanding how this part of SSIS works, mainly due to working with customers that picked up SSIS in the period when only...
February 4, 2025 at 9:33 am
Good question. I do not have much experience with Devops this way. I assume that depoying the packages/project from visual studio directly to the SSISDB repository is a 'native' process....
February 4, 2025 at 8:16 am
I basically change the connection string that SSIS builds through the GUID.
Example:
Data Source=.;Initial Catalog=NST;Provider=SQLOLEDB.1;Integrated Security=SSPI;Auto Translate=False;Application Name=SSIS-BS-{8A0D9E93-E64E-4CC7-B8DD-756F7B0E3CB2}DEV-SQL-NOOT.NST_DEV;
Then I basically change the provider in the connection string.
But if you have a connection...
December 12, 2024 at 4:42 pm
Message returned after modifying the connection string:
"The specified provider is not supported. Please choose different provider in connection manager. "
The .dll's are present in both the system32 and syswow64 folders
When...
December 12, 2024 at 3:07 pm
I do not feel that it would be different. I have no experience with this type of deployment, hence my question. If development and production would not be identical, then...
November 19, 2024 at 7:50 am
Okay Phil, that looks like an elegant alternative.
I'll test to check whether any performance difference may exist
October 19, 2024 at 12:51 pm
But what followed was a discussion of best practice, which you did not seem to agree with & that's why (I believe) people chimed in.
Sorry , but I never advocated...
September 14, 2024 at 8:11 am
A typical customer would be a small production company where in the past a consultant simply developed on one of the servers within the clients network. Back then it was...
September 13, 2024 at 4:13 pm
That still wuld require install of all components on the client workstation. As the server mentioned is solely used for staging purposes during the early morning, then database activity is...
September 3, 2024 at 3:24 pm
Okay, let me rephrase the question: What in you opinion should then be installed on that client (the one RDP'ed against) to get a workable development setup?
And yes, in some...
September 3, 2024 at 8:53 am
Don't think so. The customer would be 100 miles around the block and the solution and data itself only existed on the customers server.
No other option than to set up...
September 3, 2024 at 7:34 am
I guess this indicates that if you change the account where the 2 services are running under AFTER getting them up or while installing, then the account that is used...
July 25, 2024 at 10:49 am
The error table contains 10.000 entries, but the following message seems the most relevant?:
Microsoft.SqlServer.DataWarehouse.Common.Security.MppSecurityException[107035:1]: 107035;Dms authorization failed due to [NOOT\nootbeheer] is not member of group [PdwDataMovementAccess]
at Microsoft.SqlServer.DataWarehouse.DataMovement.Common.Security.DMSSecurityProvider.RunSecurityRoutineGetNegotiateStream(Stream stream)
at Microsoft.SqlServer.DataWarehouse.DataMovement.Common.Security.DMSSecurityProvider.RunSecurityRoutine(Stream stream,...
July 25, 2024 at 10:26 am
The only thing in the logs is the message : Failed Stream Scan. The DSN is working when used in conjunction with a linked server query, so authentication should be...
July 24, 2024 at 6:10 pm
Viewing 15 posts - 1 through 15 (of 80 total)