I am trying to dump a table with > 32 columns to a text
file. I am emphasizing "> 32 columns" because through some
basic testing it appears that when you try and dump more
than 32 columns, SQL Server takes a memory exception and
MMC blows up. I was wondering if anyone is seeing this and
if there are any known work arounds to this apprent issue.

Just an FYI I am running SQL 2k on a 2K box with the
latest SPs applied to both.

Thanx in advance,

James

We've seen a slightly different problem. When importing from a fixed length field text file, and the records are fairly long, the
connection editor goes a bit brain dead, and wont show data beyond a position, and won't set delimiters properly, and other stuff.

I think it has mostly been designed to do small test-cases, like software testers would invent, or like Duwamish. Not what you would
find in the real world.

I've posted the problem before, and no one replied. We tried to get imaginitive though, and dealt with this by saving the package to
VB, editing the VB to do the transformations we could not edit in the designer, and then do the documented tweak to save the package
from the VB back into DTS form.

Sorry to be the one to bring you the really bad news, James!


"James Lochte" <jlochte (AT) syscom (DOT) com> wrote

This is a known bug introduced with SP3

http://support.microsoft.com/default...B;EN-US;814113

--

----------------------------

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.allisonmitchell.com - Expert SQL Server Consultancy.
www.SQLDTS.com - The site for all your DTS needs.
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org


"James Lochte" <jlochte (AT) syscom (DOT) com> wrote