Is it possible to create a fixed column report?

I was just wondering if it was possible to create a fixed column report that would export to a text file as dat file to be consumed by an outside process. By this I mean that my first column would be characters 1 to 8, column 2 would be 8 to 20, column 3 would be 21 to 40, etc...

If so, how would you do it?

Thanks in advance.

David,

I had to do this for a report. I generated an XML file and applied an XSL translation to get it to fixed field ASCII. Not real difficult, but it required a second step. Don't forget to change the mime output type. I saw somewhere that you can specify the XSL file to apply after exporting to XML within Reporting Services,I just don't remember where.

R

Is bug described in article 872843 really fixed?

I'm running SQL Server 2000 SP4 with the AWE hotfix (build 2040?) on Windows
Server 2003 with replication.
This morning, my log reader agents failed. In the server log, I saw the
following messages:
SQL Server Assertion: File: <logscan.cpp>, line=1985
Failed Assertion = 'startLSN >= m_curLSN'.
...
SQL Server Assertion: File: <logscan.cpp>, line=2223
Failed Assertion = 'm_noOfScAlloc == 0'.
KB article 872843 says that this is supposed to be fixed in SP4... is it?
Or did it come back in the AWE hotfix?
Regards,
Jonathan
Hello,
KB872843 is included in SQL server 2000 SP4. It appears a new issue and is
not related to the AWE hotfix. Please reInitializing the replication and
then check if the issue still exists.
To find out the cause of this issue we may need to analyze memory dumps,
this work has to be done by contacting Microsoft Customer Service and
Support (CSS). Therefore, if the issue still exists, please contact CSS for
more immediate assistance. For more information on available CSS services,
please click here:
http://support.microsoft.com/default...roPhone#faq607

Is bug described in article 872843 really fixed?

I'm running SQL Server 2000 SP4 with the AWE hotfix (build 2040?) on Windows
Server 2003 with replication.
This morning, my log reader agents failed. In the server log, I saw the
following messages:
SQL Server Assertion: File: <logscan.cpp>, line=1985
Failed Assertion = 'startLSN >= m_curLSN'.
...
SQL Server Assertion: File: <logscan.cpp>, line=2223
Failed Assertion = 'm_noOfScAlloc == 0'.
KB article 872843 says that this is supposed to be fixed in SP4... is it?
Or did it come back in the AWE hotfix?
Regards,
JonathanHello,
KB872843 is included in SQL server 2000 SP4. It appears a new issue and is
not related to the AWE hotfix. Please reInitializing the replication and
then check if the issue still exists.
To find out the cause of this issue we may need to analyze memory dumps,
this work has to be done by contacting Microsoft Customer Service and
Support (CSS). Therefore, if the issue still exists, please contact CSS for
more immediate assistance. For more information on available CSS services,
please click here:
http://support.microsoft.com/defaul...ProPhone#faq607

Is bug described in article 872843 really fixed?

I'm running SQL Server 2000 SP4 with the AWE hotfix (build 2040?) on Windows
Server 2003 with replication.
This morning, my log reader agents failed. In the server log, I saw the
following messages:
SQL Server Assertion: File: <logscan.cpp>, line=1985
Failed Assertion = 'startLSN >= m_curLSN'.
...
SQL Server Assertion: File: <logscan.cpp>, line=2223
Failed Assertion = 'm_noOfScAlloc == 0'.
KB article 872843 says that this is supposed to be fixed in SP4... is it?
Or did it come back in the AWE hotfix?
Regards,
JonathanHello,
KB872843 is included in SQL server 2000 SP4. It appears a new issue and is
not related to the AWE hotfix. Please reInitializing the replication and
then check if the issue still exists.
To find out the cause of this issue we may need to analyze memory dumps,
this work has to be done by contacting Microsoft Customer Service and
Support (CSS). Therefore, if the issue still exists, please contact CSS for
more immediate assistance. For more information on available CSS services,
please click here:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607

Is bug 351711 fixed in MSDE 2000 SP1 or later?

I'm reading this article http://support.microsoft.com/?id=285100. I wonder
whether it is fixed or not in MSDE 2000 installation. If yes, fixed in which
SP?
The hot fix is released JAN-22-2001 and the article is Last Review : October
7, 2005. The article does not mention anything about whether the hot fix is
included in SP and it does not mention which SP does this bug applies to. By
reading the article, I will assume this only applies to MSDE 2000 without SP
and fixed in SP1. But can I assume that?Just download the latest MSDE version (Microsoft SQL Server 2000 Service Pack
4
http://www.microsoft.com/downloads/details.aspx?familyid=8E2DFC8D-C20E-4446-99A9-B7F0213F8BC5&displaylang=en
or directly from
http://www.microsoft.com/downloads/info.aspx?na=46&p=6&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=8E2DFC8D-C20E-4446-99A9-B7F0213F8BC5&u=http%3a%2f%2fdownload.microsoft.com%2fdownload%2f1%2fb%2fd%2f1bdf5b78-584e-4de0-b36f-c44e06b0d2a3%2fSQL2000.MSDE-KB884525-SP4-x86-ENU.EXE&oRef=http%3a%2f%2fwww.microsoft.com%2fdownloads%2fdetails.aspx%3fFamilyId%3d413744D1-A0BC-479F-BAFA-E4B278EB9147%26displaylang%3den
"Peter" wrote:
> I'm reading this article http://support.microsoft.com/?id=285100. I wonder
> whether it is fixed or not in MSDE 2000 installation. If yes, fixed in which
> SP?
> The hot fix is released JAN-22-2001 and the article is Last Review : October
> 7, 2005. The article does not mention anything about whether the hot fix is
> included in SP and it does not mention which SP does this bug applies to. By
> reading the article, I will assume this only applies to MSDE 2000 without SP
> and fixed in SP1. But can I assume that?

Is bug 351711 fixed in MSDE 2000 SP1 or later?

I'm reading this article http://support.microsoft.com/?id=285100. I wonder
whether it is fixed or not in MSDE 2000 installation. If yes, fixed in whic
h
SP?
The hot fix is released JAN-22-2001 and the article is Last Review : October
7, 2005. The article does not mention anything about whether the hot fix i
s
included in SP and it does not mention which SP does this bug applies to. By
reading the article, I will assume this only applies to MSDE 2000 without SP
and fixed in SP1. But can I assume that?Just download the latest MSDE version (Microsoft SQL Server 2000 Service Pac
k
4)
http://www.microsoft.com/downloads/...&displaylang=en
or directly from:
http://www.microsoft.com/downloads/...r />
.MSDE-KB8
84525-SP4-x86-ENU.EXE&oRef=http%3a%2f%2fwww.microsoft.com%2fdownloads%2fdeta
ils.aspx%3fFamilyId%3d413744D1-A0BC-479F-BAFA-E4B278EB9147%26displaylang%3de
n
"Peter" wrote:

> I'm reading this article http://support.microsoft.com/?id=285100. I wonde
r
> whether it is fixed or not in MSDE 2000 installation. If yes, fixed in wh
ich
> SP?
> The hot fix is released JAN-22-2001 and the article is Last Review : Octob
er
> 7, 2005. The article does not mention anything about whether the hot fix
is
> included in SP and it does not mention which SP does this bug applies to.
By
> reading the article, I will assume this only applies to MSDE 2000 without
SP
> and fixed in SP1. But can I assume that?