Re: DTExec slow

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

It was actually this way before SP1 as well. The only thing that
SP1 has changed is that some files got signed by new certificate,
so CryptoAPI has to validate two certificates instead of one, and
it may take twice more time.

If this check introduces significant delays, your firewall
might be incorrectly configured (see details in kb 918644:
http://support.microsoft.com/kb/918644)

Regards,
Michael.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Francisco A. Gonzalez" <fgonzalez@xxxxxxxxxx> wrote in message news:u7j$k3wnHHA.4424@xxxxxxxxxxxxxxxxxxxxxxx
to ilustrate more:
The thing is that when you execute a package (after installing SP1), CryptoAPI, on behalf of the SSIS service, attempts to go out to the internet to check a certificate revocation list.

cheers

--

Francisco A. Gonzalez
fgonzalez@xxxxxxxxxx



"DC" <dc@xxxxxxxxx> wrote in message news:1180078037.881623.105720@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi Francisco,

when I read your message I thought "Impossible! This guy must be
joking." but of course I tried it anyway and deactivated the option
you mentioned on the SQL Server machine and it WORKS! Execution time
almost one minute when the option is checked, about three seconds when
it is not checked. Do you know more tricks like that?

Thanks a lot!

Regards
DC

On 23 Mai, 16:27, "Francisco A. Gonzalez" <fgonza...@xxxxxxxxxx>
wrote:
Hi

I have seen this problem with sp1.
Check this.
Go to the user that execute the package and Control panel, internet options,
advanced, and uncheck check for publishers revocation certificate.

cheers

--

Francisco A. Gonzalez
fgonza...@xxxxxxxxxx

"DC" <d...@xxxxxxxxx> wrote in message

news:1179928967.373341.186340@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



> Good day,

> when I execute a simple DTS package from DTS Designer in Visual
> Studio, it takes 5 Seconds to execute. The same package lasts about 50
> seconds when I start it via DTExec in a stored procedure. I can see in
> the verbose output of the package, that it must have done nothing most
> of the time, it starts to execute the actual tasks in the last five
> seconds.

> Is there a fix for this or a better way to launch a package from a
> stored proc?

> Thanks in advance for any hint,

> Regards
> DC- Zitierten Text ausblenden -

- Zitierten Text anzeigen -





.

Relevant Pages

  • Re: Cross-database execution permissions with certificates and sch
    ... Whatever principal you impersonate with EXECUTE AS must have a security context in both databases but it doesn't need to be dbo. ... CREATE USER dispatcher ... The reason EXECUTE AS OWNER works with dbo as the schema owner is that 1) the certificate is a trusted authenticator because you granted AUTHENTICATE and 2) the impersonated dbo principal exists in dispatchDB by virtue of the fact that both databases are owed by the same server principal. ... You can still use the certificate as the authenticator as long as the impersonated principal has a security context in the referenced database as well. ...
    (microsoft.public.sqlserver.security)
  • Re: Cross-database execution permissions with certificates and sch
    ... activated user cannot access objects in other schemas in this database. ... injection is defended against, however, the threat exists anywhere EXECUTE ... CREATE USER dispatcher ... the certificate is a trusted authenticator because you granted AUTHENTICATE ...
    (microsoft.public.sqlserver.security)
  • Re: Auto Enrollment not working for one DC
    ... I was already aware of the post SP1 problem with the CERTSVC_DCOM_ACCESS ... Certificate Services: Effects of security enhancements to the DCOM protocol ...
    (microsoft.public.windows.server.active_directory)
  • Cross-database execution permissions with certificates and schemas
    ... make the dispatcher user the owner (EXEC sp_addrolemember N'db_owner', ... Discard the private key from the certificate, ... make the provider user the owner (EXEC sp_addrolemember N'db_owner', ... execute [dispatch] ...
    (microsoft.public.sqlserver.security)
  • Re: Package Instance Security Rights
    ... Best approach would be to upgrade your site to SMS 2003 SP1 or to get hotfix ... This posting is provided "AS IS" with no warranties, and confers no rights. ... >> If they right click on a class, collection, or package and select All ...
    (microsoft.public.sms.swdist)