RE: SSIS Question - Solved

RE: SSIS Question - Solved

 

  


Well thanks for the flood of replies... it's really heart-warming....

The issue isn't with the app, it's with SSIS.
I'm sure you're aware that SSIS is 32bit only, SSIS won't work on a 64bit
SQL box.
So if you're thinking of migrating to a wondey 64bit environment, don't
expect to host SSIS on the same box. Oh it'll install, it just won't
work.... not according to Microsoft anyway... D'Oh!!
They never made a 64bit version. It'll run via command line, but who wants
to go commando in a 64bit environment???
So we have to launch/schedule the task within a 32bit machine to build the
cube on the 64bit machine....

Thanks again....

Jeremy
Fenris Software Consuilting, Inc


>From: "Jeremy Greaves "
><mssqldba-ezmlmshield-x16735158.[Email address protected]
>To: "LazyDBA Discussion" <[Email address protected]
>Subject: SSIS Question
>Date: Thu, 27 Sep 2007 12:09:23 -0400
>
>Gurus,
>
>I have a semaphore record in a table, which is then being used to help time
>a job task, so that it will run once certain data has been successfully
>updated.
>
>Which SSIS script can I use to determine if a SQL statement returns a row.
>Here is the SQL:
>
>SELECT LAST_EXTRACT_DT
>FROM <TableName>
>WHERE JOB_NM = 'WW_SALES' and LAST_EXTRACT_DT = convert(varchar(8),
>getdate(), 112)
>
>So, if the LAST_EXTRCT_DT field has todays date in it(i.e. the data refresh
>has occurred and that process has flagged the date with "today"), I'll get
>a
>row returned, if it hasn't been updated to todays date, then nada....
>
>Having done that I then need to return a "Success" or "Fail" conditional
>allowing the process to continue..
>
>Oh, and one last wrinkle... once "our" SSIS script has been fired at it's
>scheduled time, it then needs to sleep and loop until this date flag has
>been set to "today" for it to continue.
>
>I had written a VB.Net proggy to do this, which works (d'uh). However, on
>the server for which it was intended the .exe is not even running, so the
>Win32 Execute Process Task SSIS control returns a failed state. I know it's
>not running as the Logfile the VB.Net proggy writes to isn't even being
>created and written to.
>
>Obi Wan's, your help would be greatly appreciated.
>
>
>
>
>---------------------------------------------------------------------
>TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
>To post a dba job: http://jobs.lazydba.com
>To subscribe : http://www.LazyDBA.com
>To unsubscribe: http://www.lazydba.com/unsubscribe.html
>



MS Sql Server LazyDBA home page