SSIS 2008

More
10 years 9 months ago #119 by Moderator
Moderator replied the topic: Re: SSIS 2008
Not in the first release. I think we'll add multi-statement support in one if the updates/service packs for 1.3.

Please Log in or Create an account to join the conversation.

More
10 years 9 months ago #121 by shoubs
shoubs replied the topic: Re: SSIS 2008
For some reason, I don't seem to be able to send email to any of your addresses.

Here is what I sent minus my details.

Dear Support,

I’ve been on the forum having a discussion with Moderator (<!-- l --><a class="postlink-local" href=" pgoledb.com/forum/viewtopic.php?f=4&...pic.php?f=4&t=49 [/url]<!-- l -->). There have been a number of bugs in the provider that I’ve discovers and have been fixed (quickly, which we are grateful for).
I’m concerned that we're wasting a fair bit of time discovering bugs, and we need to test everything and ensure our requirements are met (especially regarding performance) before we consider purchasing licences. Would it be possible to obtain a single full licence, free of change, to ensure this is the correct product for us?

Kind Regards

Dan

Please Log in or Create an account to join the conversation.

More
10 years 9 months ago #122 by shoubs
shoubs replied the topic: Re: SSIS 2008
I may have found another bug?

When I run the following, (i'm trying to map to dbtimestamp, but I have tried all date and time types) the debugger crashes - with SSIS Debug Host has stopped working, if i try to parse the query, BIDS crashes! I don't have this problem when doing something simular with the update.

INSERT INTO aacustomer
SELECT a.customerid, a.siteid, a.fname, a.sname, a.email, a.tel, a.mobile, a.status, a.sitecode, a.tstamp, a.title, a.customeruuid, a.postcode, ?
FROM tmp_aacustomer a
LEFT JOIN aacustomer b ON a.customerid = b.customerid
WHERE b.customerid IS NULL;

If I click show problem details, it doesn't really help, other than saying the problem is in PGNP.dll

Problem signature:
Problem Event Name: BEX
Application Name: DtsDebugHost.exe
Application Version: 2007.100.1600.22
Application Timestamp: 48753d31
Fault Module Name: PGNP.dll
Fault Module Version: 1.3.0.2096
Fault Module Timestamp: 4ad493cf
Exception Offset: 00130bcc
Exception Code: c000000d
Exception Data: 00000000
OS Version: 6.0.6002.2.2.0.256.6
Locale ID: 2057
Additional Information 1: 6625
Additional Information 2: ca23f8d3960349a70c0e33720c5fb852
Additional Information 3: 3ec1
Additional Information 4: 326df405faf139be909750d051faaa5b

Please Log in or Create an account to join the conversation.

More
10 years 9 months ago #123 by Moderator
Moderator replied the topic: Re: SSIS 2008
Dan,
I have notified my host provider about the e-mail issues. In the mean time I will send you my other e-mail address that you can use for communication.

We will start working on the fix shortly.
Thank you,
Konstantin

Please Log in or Create an account to join the conversation.

More
10 years 9 months ago #125 by shoubs
shoubs replied the topic: Re: SSIS 2008
Thanks for the reply, I've sent you an email to that address with the schema's.

I'm sure this one will get to you, but just for the board:

Can you confirm that the full version 1.3 you release properly will contain all the features in 1.3.2096?

and I possibly found a minor bug today:

when you
select count(colName) as updatedcount from tbl where archivemodificationdate = ?
you get a message saying

The query failed to parse. Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

however if I remove the where -
select count(colName) as updatedcount from tbl
it parse's fine



another parse problem (possibly the same as reported earlier - has a parameter):

BIDS crashes if I try and parse the following query -
update auditpackage set enddate = current_timestamp,success = true, totalextract = totalextract + ?, totalinsert = totalinsert + ?, totalupdate = totalupdate + ? where idaudit = ?
with this detil:

Problem signature:
Problem Event Name: BEX
Application Name: devenv.exe
Application Version: 9.0.30729.1
Application Timestamp: 488f2b50
Fault Module Name: PGNP.dll
Fault Module Version: 1.3.0.2096
Fault Module Timestamp: 4ad493cf
Exception Offset: 00130bcc
Exception Code: c000000d
Exception Data: 00000000
OS Version: 6.0.6002.2.2.0.256.6
Locale ID: 2057
Additional Information 1: 3fbb
Additional Information 2: 1524889db36223a8bec167d7676a8cb4
Additional Information 3: 96ef
Additional Information 4: 01e9bd5a8cca95216372cf2833a3ac4e

Please Log in or Create an account to join the conversation.

More
10 years 9 months ago #126 by shoubs
shoubs replied the topic: Re: SSIS 2008
I think this might be another potential bug.

I've added a new item from a template package I've created. But I seem to (in BIDS) have to run it then restart it for it to start running (every time). I get this complie time error:

SSIS package "ArchiveVHCTCO.dtsx" starting.
Error: 0xC0202009 at Transfer rows changed since last ran, OLE DB Source 1 [483]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "PGNP" Hresult: 0x00000000 Description: "Undefined table vhc_tco".
Error: 0xC004706B at Transfer rows changed since last ran, SSIS.Pipeline: "component "OLE DB Source 1" (483)" failed validation and returned validation status "VS_ISBROKEN".
Error: 0xC004700C at Transfer rows changed since last ran, SSIS.Pipeline: One or more component failed validation.
Error: 0xC0024107 at Transfer rows changed since last ran: There were errors during task validation.
SSIS package "ArchiveVHCTCO.dtsx" finished: Failure.


Theres nothing wrong with task "Transfer rows changed since last ran" and it runs fine if you execute task on it, the table definitely exists.

Please Log in or Create an account to join the conversation.

More
10 years 9 months ago #130 by Moderator
Moderator replied the topic: Re: SSIS 2008
Dan, please allow us a few days to work on these issues. Thank you tons for contributing into the project!!

Please Log in or Create an account to join the conversation.

More
10 years 9 months ago #131 by shoubs
shoubs replied the topic: Re: SSIS 2008
Sure, no problem. Thank you for replying with useful comments over the past week or two.
Other times I've been in a situation where I'm testing out various solutions and you come across bugs, no one wants to know.

I'm eager to get on and test performance now. Are you still on course for a release on Monday?


Had a bug when I tried to add a parameter in the OLEDB Source componet - it crashed BIDs, once you restart the bug goes away for a while, but eventually comes back.
Its another case of trying to access protected memory. It might have something to do with writing a incorrect statement then clicking paramter, then correcting the statement and clicking parameters again...?

Problem signature:
Problem Event Name: APPCRASH
Application Name: devenv.exe
Application Version: 9.0.30729.1
Application Timestamp: 488f2b50
Fault Module Name: PGNP.dll
Fault Module Version: 1.3.0.2096
Fault Module Timestamp: 4ad493cf
Exception Code: c0000005
Exception Offset: 000b2f5d
OS Version: 6.0.6002.2.2.0.256.6
Locale ID: 2057

Additional information about the problem:
LCID: 1033

Please Log in or Create an account to join the conversation.

More
10 years 9 months ago #132 by Moderator
Moderator replied the topic: Re: SSIS 2008
Yep, version 1.3 is going to be released on Monday.

I have sent you another trial build with some fixes.

Please Log in or Create an account to join the conversation.

More
10 years 9 months ago #134 by shoubs
shoubs replied the topic: Re: SSIS 2008
Thanks, I'm using the version you've sent me.
But have a couple of major issues with it:

When I want to insert about 3 million rows (and I expect this will happen on the update too) - using the following syntax:
insert into tbl select from a left join b where b.id is null

and get the following error AFTER 30 seconds:

Error: 0xC002F210 at Insert data, Execute SQL Task: Executing the query "INSERT INTO..." failed with the following error: "timeout expired".


I've tried various values for timeout's on the task itself and the connection, I've even looked in the configuration file in postgres. There could be a setting I am missing (likley) or could this be something to do with the provider (prehaps command timeout - not connection timeout)?

________

Another problem I have is when I click ok on the SQL source container edit screen, BIDS crashes when I try to convert a character varying to a timestamp in the where clause (if I leave out the cast() it says I must do it explicitly):
WHERE CAST(to_timestamp(tstamp, 'DD/MM/YYYY HH24:MI:SS') AS timestamp without time zone) > ?

Please Log in or Create an account to join the conversation.

More
10 years 9 months ago #136 by Moderator
Moderator replied the topic: Re: SSIS 2008
Have you tried to add COMMAND_TIMEOUT=3000 to Extended Properties of the connection string?

I recommend enabling bulk insert for the highest speed, e.g. add following parameters to the Extended Properties:
...;BULK_METHOD=COPY;BULK_INSERT=5000;...

Depending on speed of your hardware and average row length, import speed can vary, but in many cases it exceeds 1/4 million rows a sec.

We have reproduced issue with cast. We'll send you build with fix shortly.

Please Log in or Create an account to join the conversation.

More
10 years 9 months ago #137 by shoubs
shoubs replied the topic: Re: SSIS 2008
Brilliant! Bug fixes works. I've some more testing todo today.

I think the box we're using will be replaced with a 64-bit version of Server 2008. So I'm going to have to go though all the testing again soon. Are there any differences between the 32-bit and 64-bit provider?
__________________________________________

I found a problem with parameters when trying to add datetime variables (set to DBTIMESTAMP in sql task) to a timestamp without timezone column. No errors are thrown and the package runs fine, but well, here's an example:
18/07/1983 14:21 maps to 19085-08-18 21:00:00
and
01/01/2000 00:00:00 to 0151-08-17 01:00:00

I can't see anything I'm doing wrong - the documentation mentions something about DBTYPE_DBTIMESTAMP which I assume is DBTIMESTAMP.

_________________________________________

This ones quite annoying, but I've found a solution to it, - I moved the packages onto the production server, but when I run it, bids gets to the Data Flow Task and cancels the package - the SQL Dumper window appears momentarily and outputs to a file. I fixed this by removing all datasources and all connections from all packages, then added them again.


__________________________________________

Last problem - sometimes the oledb source won't transfer the rows - you can click preview and the rows are there, but when you execute the task, it just turns green, (as if it isn't even running), no pause to think, nothing, doesn't even report 0 rows. any ideas?

Thanks.
-Dan

Please Log in or Create an account to join the conversation.

More
10 years 9 months ago #138 by Moderator
Moderator replied the topic: Re: SSIS 2008

Are there any differences between the 32-bit and 64-bit provider?

Very few. Except obvious 64-bit pointers and virtually unlimited memory size, some assembler functions were rewritten in C++. Fortunately it did not affect performance much.

18/07/1983 14:21 maps to 19085-08-18 21:00:00

Do you cast datetime to string before processing? Provider expects following format: YYYYMMDD hh:mm:ss.

Last problem - sometimes the oledb source won't transfer the rows <<cut>>

I have not been able to reproduce this. Is there a specific package or some condition that can help reproduce it?

Please Log in or Create an account to join the conversation.

More
10 years 9 months ago #139 by shoubs
shoubs replied the topic: Re: SSIS 2008
I will try the casting, but unfortuanly I can't run the packages at the moment (since transferring them)

Amongst other problems (everything going green but doing nothing, and sometimes data flow task stalls on yellow once everything in it is complete) visual studio crashes when I click ok after clicking on mapping in the oledb destination - says
AppName: devenv.exe
AppVer: 9.0.30729.1
AppStamp: 488f2b50
&#91;b&#93;ModName: pgnp.dll, &#91;/b&#93;
ModVer: 1.3.0.2101
ModStamp: 4ae67ce9
fDebug: 0
Offset: 000edbe1


I deleted the data flow task and recreated it - after the crash I make sure it looks ok then run it, - it stalls on the task (as in my previous post when it turns yellow) and outputs the following to an sql dumper error log (note that there arn't any parameters in the dataflow task, I removed them all):

(36C:B94) 10/28/09 10:26:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
(36C:B94) 10/28/09 10:26:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 1: 4040
(36C:B94) 10/28/09 10:26:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 2: 0
(36C:B94) 10/28/09 10:26:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 3: 0:0
(36C:B94) 10/28/09 10:26:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 4: 0100D608
(36C:B94) 10/28/09 10:26:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
(36C:B94) 10/28/09 10:26:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 4040
(36C:B94) 10/28/09 10:26:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
(36C:B94) 10/28/09 10:26:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
(36C:B94) 10/28/09 10:26:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags = 0x0
(36C:B94) 10/28/09 10:26:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x0100D608
(36C:B94) 10/28/09 10:26:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
(36C:B94) 10/28/09 10:26:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordPtr = 0x00000000
(36C:B94) 10/28/09 10:26:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x00000000
(36C:B94) 10/28/09 10:26:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
(36C:B94) 10/28/09 10:26:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName = <NULL>
(36C:B94) 10/28/09 10:26:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
(36C:B94) 10/28/09 10:26:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
(36C:B94) 10/28/09 10:26:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
(36C:B94) 10/28/09 10:26:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
(36C:B94) 10/28/09 10:26:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files\Microsoft SQL Server\100\Shared\ErrorDumps\SQLDmpr0013.mdmp
(36C:B94) 10/28/09 10:26:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'c:\Program Files\Microsoft SQL Server\100\Shared\dbghelp.dll'
(36C:B94) 10/28/09 10:26:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'c:\Program Files\Microsoft SQL Server\100\Shared\dbghelp.dll' : '6.8:4.0'
(36C:B94) 10/28/09 10:26:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'c:\Program Files\Microsoft SQL Server\100\Shared\dbghelp.dll' : '6.8:4.0'
(36C:B94) 10/28/09 10:26:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'c:\Program Files\Microsoft SQL Server\100\Shared\SQLDUMPER.EXE'
(36C:B94) 10/28/09 10:26:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'c:\Program Files\Microsoft SQL Server\100\Shared\SQLDUMPER.EXE' : '2007.100:1600.22'
(36C:B94) 10/28/09 10:26:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'c:\Program Files\Microsoft SQL Server\100\Shared\SQLDUMPER.EXE' : '10.0:1600.22'
(36C:B94) 10/28/09 10:26:42, ACTION, DtsDebugHost.exe, Watson Invoke: No


It looks like I'm going to have to bin all the work I've done and start again from scratch. SSIS is crap when it comes to moving packages from one server to another.

Please Log in or Create an account to join the conversation.

More
10 years 9 months ago #140 by shoubs
shoubs replied the topic: Re: SSIS 2008
I changed to using XML config files, which stopped the stalling, but now I'm back to everything turning green and doing nothing. I recreated a package from scratch and it seems to work fine. Looks like I'll be working evenings and weekends for the next week or two to catch back up. SSIS is great when it works, but absolute shite when it doesn't.

Please Log in or Create an account to join the conversation.

More
10 years 9 months ago #141 by shoubs
shoubs replied the topic: Re: SSIS 2008
I looked in pg_stat_activity - the connection is being opened, but nothing is being run, the query just say IDLE.

This is a big problem, I can't see why this is happening, or anything in google about it :(

Looks like I'm going to have to create everything from scratch on the new server, which is a right bugger as I'm going to have to do this again when we move servers next month.

Please Log in or Create an account to join the conversation.

Time to create page: 0.089 seconds
Powered by Kunena Forum