![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I have a problem with creating a DTS package, SQL 2K. At first, transform data to file generates memory error. Therefore, I found an article KB814113 and microsoft's explanation that is a bug of SP3. I couldn't found a hot fix, and made a fresh installation of SQL server, without SP3. Now, making files from some tables works properly, bat for some tables invokes a similar memory protection fault. I think that is a problem on table's size. Table have a 98 columns and row size 1278 (SELECT Sum(length) FROM syscolumns WHERE id=OBJECT_ID('tablename') . Exporttables with 35 columns works properly, export tables with 40 columns doesn't. And, is it possible to distribute packages from SQL2K SP2 to SQL2K SP3? Any help??? |
#3
| |||
| |||
|
#4
| |||
| |||
|
|
No, I can't create a package. Problem explained in KB814113 I temorary resolved. Now I am using SQL2K SP2, and for some tables I create package succesfully, for some tables don't!!! Is it a problem of table's size or numbers of columns??? sasa *** Sent via Developersdex http://www.developersdex.com *** Don't just participate in USENET...get rewarded for it! |
#5
| |||
| |||
|
#6
| |||
| |||
|
|
Actualy, When I export "big" table (over a 40 columns) through dts wizard, and when I choose option Save, it's work OK, and a package is saved on SQL server. Then, when I want to edit saved package through SQL enterprice manager, memory protection fault is generated. Is it a EM bug??? sasa *** Sent via Developersdex http://www.developersdex.com *** Don't just participate in USENET...get rewarded for it! |
![]() |
| Thread Tools | |
| Display Modes | |
| |