none
SQL Server Agent job (Execute Package Utility) is running for 32 bit whereas SSMS and OS is 64 bit. Any idea WHY? RRS feed

  • Question

  • Hi All,

    There is a SSIS package to execute processing of SSAS DB(process server) and then sync to another SSAS DB(query server), which is configured under SQL Server Agent Job. I ran it by click on 'Start job at step..' and it went successful. I noticed below content of message in 'View History' for same job:

    "Executed as user: XX\YYYYYYY. Microsoft (R) SQL Server Execute Package Utility  Version 12.0.6205.1 for 32-bit  Copyright (C) Microsoft Corporation. All rights reserved.    Started:  4:11:27 PM  Execution ID: 7090352.  To view the details for the execution, right-click on the Integration Services Catalog...."

    I rechecked and confirmed SQL Server installation is 64 bit only, but why I got this message which is saying Execute Package Utility ran as 32 bit. how this is possible? I gone through below documentation of Microsoft but it doesn't say what i want to know. Also it is guiding how to run this in 32 bit env whereas I am looking for 64 bit env.

    https://support.microsoft.com/en-my/help/934653/how-to-use-the-64-bit-sql-server-agent-to-schedule-a-sql-server-2005-i

    can anyone please help on this, why it is showing as 32 bit bit in message? And how can I make/run it under 64 bit? will there be any consequences of it if runs under 64 bit?

    Any hints, comments, guide, help will be highly appreciated.

    Thanks in Advance,




    • Edited by ScriptSoft Wednesday, October 9, 2019 7:06 AM
    Wednesday, October 9, 2019 7:05 AM

Answers

All replies

  • I got this message which is saying Execute Package Utility ran as 32 bit. how this is possible?

    Pretty easy, you can define in a SSIS Job step to use the 32-bit runtime, e.g. when the package utilze a 32 bit data Provider.

    See Run Integration Services (SSIS) Packages => 32-bit runtime


    Olaf Helper

    [ Blog] [ Xing] [ MVP]

    • Marked as answer by ScriptSoft Thursday, October 10, 2019 3:20 AM
    Wednesday, October 9, 2019 8:42 AM
  • duplicate on SO
    Wednesday, October 9, 2019 12:16 PM
  • This is only barely related...but SQL 64-bit makes sense, SSMS is always 32-bit, isn't it?  Just from the post title and for future readers of this thread

    22 years of database experience, most with SQL Server. Please 'Mark as answered' those posts that helped you.

    • Marked as answer by ScriptSoft Thursday, October 10, 2019 3:20 AM
    Wednesday, October 9, 2019 12:26 PM
  • Hello Kevin,

    Many thanks for your response. When I ran command "SELECT SERVERPROPERTY('edition')" in SQL window to find the SQL server edition, it gave me result as "Enterprise-Core Edition (64-bit)" which I understood as SSMS is 64-bit. Am I interpreting something wrong out of it? Can you please guide? Thanks




    • Edited by ScriptSoft Wednesday, October 9, 2019 3:54 PM
    Wednesday, October 9, 2019 3:54 PM
  • Hello Kevin,

    Many thanks for your response. When I ran command "SELECT SERVERPROPERTY('edition')" in SQL window to find the SQL server edition, it gave me result as "Enterprise-Core Edition (64-bit)" which I understood as SSMS is 64-bit. Am I interpreting something wrong out of it? Can you please guide? Thanks


    That is the SQL Server Engine version.  SSMS is just a 32-bit application tool you use to connect to SQL Engine.




    22 years of database experience, most with SQL Server. Please 'Mark as answered' those posts that helped you.

    Wednesday, October 9, 2019 4:14 PM
  • Many thanks Kevin and Olaf for your assistance.

    Regards,




    • Edited by ScriptSoft Thursday, October 10, 2019 3:21 AM
    Thursday, October 10, 2019 3:21 AM