Float Datatype Truncation Bug

Hi Friends,

I have a table

Create table #table1(a float)

insert into #table1 values(123456789.987654321)

select a from #table1

drop table #table1

when i run this in SQLServer 2005 Management Studio i get the following truncated output

(1 row(s) affected)

a

-

123456789.987654

(1 row(s) affected)

when i run this query using SQL Query Analyser or OSQL Utility i get the following output

(1 row(s) affected)

a
--
123456789.98765431

(1 row(s) affected)

I want the full output in SQLServer 2005 itself.... Is this a microsoft bug?

I would like to know how to fix this?

Thanks and Regards,

It is not a bug. Your data is not truncated on the table(while storing). its bcs of the Management Console only.(MC result only truncate the values). Connect the same SQL Server 2005 from QA you will get the same result as 2000 (in your case your proper result).

If you want to trust your result use the following query.(explicit precision setting)

Code Snippet

Create table #table1(a float)

Insert into #table1 values(123456789.987654321)

Select cast(a as numeric(38,8)) from #table1

Drop table #table1

flat file connection bug

What happens is that the flat file connection non of the columns can be altered

you can set them in other ssis packages but not in the one that you want to use and when it comes to changes the flat file complains that not a correct file is set, even though there is one set,

and when it comes to altering a flat file source it complains that it can not find the connection and the database destination can not find the meta data BUT

when it is run it works perfectly,

so what i have had to resort to is making the part of the dts package in another package and then copying it accross

Do you have delay validation on the connection or source, or are you working off line.

Some of the components don't handle these states very elegantly.

|||

I do not know what you mean buy delay validation, but i am working on the server, connected to the server on the same mechine. the connection string is set to a variable that is set in a file loop, but when i remove, the variable and try it again it stil does not work...

|||

on the top menu you must check that the ssis drop down is not set to offline

flat file connection bug

What happens is that the flat file connection non of the columns can be altered

you can set them in other ssis packages but not in the one that you want to use and when it comes to changes the flat file complains that not a correct file is set, even though there is one set,

and when it comes to altering a flat file source it complains that it can not find the connection and the database destination can not find the meta data BUT

when it is run it works perfectly,

so what i have had to resort to is making the part of the dts package in another package and then copying it accross

Do you have delay validation on the connection or source, or are you working off line.

Some of the components don't handle these states very elegantly.

|||

I do not know what you mean buy delay validation, but i am working on the server, connected to the server on the same mechine. the connection string is set to a variable that is set in a file loop, but when i remove, the variable and try it again it stil does not work...

|||

on the top menu you must check that the ssis drop down is not set to offline

FixedHeader JavaScript Bug?

Hi
I have a report with a table containing 26 columns, the tableheader is fixed when scrolling (nice) and I have set the leftmost column to FixedHeader. It is possible via paramters for the user to select which columns that should be visible. But when some columns not are visible then I get a script exception after rendering, 'children.0.style' is null or not an object, resulting in no fixed headers at all.

If I remove som columns so that there is only 18... it works.
Seems lika bug to me?
Where can I supply bug reports, I also have one upgrading bug concerning code page?

Regards

I can take care of getting the issue investigated and verified. Do you have a sample RDL file you can post here? That would be helpful in reproducing the bug.|||

Hi!
Thank You for youre response.
I can send You the .rdl if I only had some way of contact You. I dont want to publish it here.
Look at my profile for my e-mail.

|||

Hi

I too have this same problem.

When i am previewing the rdl file, the header is getting fixed But when

i try to see the report throgh the report viewer from the web page the header is not getting fixed

and i am getting a javascript error children.0.style is null or not an object

Can anybody suggest a way to deal with this problem?

|||

Hi Fredrike

Did you get any solution to fix the header of a rdl file which was showing the javascript error

children.0.style is null or not an object ?

Can you give me some solutions to solve this issue?

my mail id is bikram.mallick@.lntinfotech.com

Thank you

Vikram

|||

There are some fixes to bugs in fixed headers in SP2. Without more details, there is no way I can know if these apply to your situation.

Can you post an rdl file that is causing this problem?

|||

Hi Fredrike

Did you get any solution to fix the header of a rdl file which was showing the javascript error

children.0.style is null or not an object ?

Can you give me some solutions to solve this issue?

my mail adds is it@.foodchina.com.tw

Thank you

Johnny from Taiwan

|||

I have just had the same problem and in my case it appears to have been caused by cells being merged in a row that are across both fixed and scrolling columns. I had to re-design my report so that the cells in the fixed columns are not merged with any that are not fixed, then it worked fine.

|||

Hi, no sorry no fix. No one contacted me and now I have left that customer so... can't send no .rdl.

I hope someone else finds the proper solution and posts here.

Regards

/Fredrike

FixedHeader JavaScript Bug?

Hi
I have a report with a table containing 26 columns, the tableheader is fixed when scrolling (nice) and I have set the leftmost column to FixedHeader. It is possible via paramters for the user to select which columns that should be visible. But when some columns not are visible then I get a script exception after rendering, 'children.0.style' is null or not an object, resulting in no fixed headers at all.

If I remove som columns so that there is only 18... it works.
Seems lika bug to me?
Where can I supply bug reports, I also have one upgrading bug concerning code page?

Regards

I can take care of getting the issue investigated and verified. Do you have a sample RDL file you can post here? That would be helpful in reproducing the bug.|||

Hi!
Thank You for youre response.
I can send You the .rdl if I only had some way of contact You. I dont want to publish it here.
Look at my profile for my e-mail.

|||

Hi

I too have this same problem.

When i am previewing the rdl file, the header is getting fixed But when

i try to see the report throgh the report viewer from the web page the header is not getting fixed

and i am getting a javascript error children.0.style is null or not an object

Can anybody suggest a way to deal with this problem?

|||

Hi Fredrike

Did you get any solution to fix the header of a rdl file which was showing the javascript error

children.0.style is null or not an object ?

Can you give me some solutions to solve this issue?

my mail id is bikram.mallick@.lntinfotech.com

Thank you

Vikram

|||

There are some fixes to bugs in fixed headers in SP2. Without more details, there is no way I can know if these apply to your situation.

Can you post an rdl file that is causing this problem?

|||

Hi Fredrike

Did you get any solution to fix the header of a rdl file which was showing the javascript error

children.0.style is null or not an object ?

Can you give me some solutions to solve this issue?

my mail adds is it@.foodchina.com.tw

Thank you

Johnny from Taiwan

|||

I have just had the same problem and in my case it appears to have been caused by cells being merged in a row that are across both fixed and scrolling columns. I had to re-design my report so that the cells in the fixed columns are not merged with any that are not fixed, then it worked fine.

|||

Hi, no sorry no fix. No one contacted me and now I have left that customer so... can't send no .rdl.

I hope someone else finds the proper solution and posts here.

Regards

/Fredrike

FixedHeader JavaScript Bug?

Hi
I have a report with a table containing 26 columns, the tableheader is fixed when scrolling (nice) and I have set the leftmost column to FixedHeader. It is possible via paramters for the user to select which columns that should be visible. But when some columns not are visible then I get a script exception after rendering, 'children.0.style' is null or not an object, resulting in no fixed headers at all.

If I remove som columns so that there is only 18... it works.
Seems lika bug to me?
Where can I supply bug reports, I also have one upgrading bug concerning code page?

Regards

I can take care of getting the issue investigated and verified. Do you have a sample RDL file you can post here? That would be helpful in reproducing the bug.|||

Hi!
Thank You for youre response.
I can send You the .rdl if I only had some way of contact You. I dont want to publish it here.
Look at my profile for my e-mail.

|||

Hi

I too have this same problem.

When i am previewing the rdl file, the header is getting fixed But when

i try to see the report throgh the report viewer from the web page the header is not getting fixed

and i am getting a javascript error children.0.style is null or not an object

Can anybody suggest a way to deal with this problem?

|||

Hi Fredrike

Did you get any solution to fix the header of a rdl file which was showing the javascript error

children.0.style is null or not an object ?

Can you give me some solutions to solve this issue?

my mail id is bikram.mallick@.lntinfotech.com

Thank you

Vikram

|||

There are some fixes to bugs in fixed headers in SP2. Without more details, there is no way I can know if these apply to your situation.

Can you post an rdl file that is causing this problem?

|||

Hi Fredrike

Did you get any solution to fix the header of a rdl file which was showing the javascript error

children.0.style is null or not an object ?

Can you give me some solutions to solve this issue?

my mail adds is it@.foodchina.com.tw

Thank you

Johnny from Taiwan

|||

I have just had the same problem and in my case it appears to have been caused by cells being merged in a row that are across both fixed and scrolling columns. I had to re-design my report so that the cells in the fixed columns are not merged with any that are not fixed, then it worked fine.

|||

Hi, no sorry no fix. No one contacted me and now I have left that customer so... can't send no .rdl.

I hope someone else finds the proper solution and posts here.

Regards

/Fredrike

FixedHeader JavaScript Bug?

Hi
I have a report with a table containing 26 columns, the tableheader is fixed when scrolling (nice) and I have set the leftmost column to FixedHeader. It is possible via paramters for the user to select which columns that should be visible. But when some columns not are visible then I get a script exception after rendering, 'children.0.style' is null or not an object, resulting in no fixed headers at all.

If I remove som columns so that there is only 18... it works.
Seems lika bug to me?
Where can I supply bug reports, I also have one upgrading bug concerning code page?

Regards

I can take care of getting the issue investigated and verified. Do you have a sample RDL file you can post here? That would be helpful in reproducing the bug.|||

Hi!
Thank You for youre response.
I can send You the .rdl if I only had some way of contact You. I dont want to publish it here.
Look at my profile for my e-mail.

|||

Hi

I too have this same problem.

When i am previewing the rdl file, the header is getting fixed But when

i try to see the report throgh the report viewer from the web page the header is not getting fixed

and i am getting a javascript error children.0.style is null or not an object

Can anybody suggest a way to deal with this problem?

|||

Hi Fredrike

Did you get any solution to fix the header of a rdl file which was showing the javascript error

children.0.style is null or not an object ?

Can you give me some solutions to solve this issue?

my mail id is bikram.mallick@.lntinfotech.com

Thank you

Vikram

|||

There are some fixes to bugs in fixed headers in SP2. Without more details, there is no way I can know if these apply to your situation.

Can you post an rdl file that is causing this problem?

|||

Hi Fredrike

Did you get any solution to fix the header of a rdl file which was showing the javascript error

children.0.style is null or not an object ?

Can you give me some solutions to solve this issue?

my mail adds is it@.foodchina.com.tw

Thank you

Johnny from Taiwan

|||

I have just had the same problem and in my case it appears to have been caused by cells being merged in a row that are across both fixed and scrolling columns. I had to re-design my report so that the cells in the fixed columns are not merged with any that are not fixed, then it worked fine.

|||

Hi, no sorry no fix. No one contacted me and now I have left that customer so... can't send no .rdl.

I hope someone else finds the proper solution and posts here.

Regards

/Fredrike

First 4 symbols of a string truncated when inserting typed XML

Dear SQL experts, is it a bug or I'm understanding something wrong?

Please look at the script below. Is it a bug? If yes, when can we expect it to be fixed and released? Are there any workarounds apart from just not using xsd:string type?

IF EXISTS (SELECT * FROM sys.xml_schema_collections c, sys.schemas s WHERE c.schema_id = s.schema_id AND (quotename(s.name) + '.' + quotename(c.name)) = N'[dbo].[TestSchema]')

DROP XML SCHEMA COLLECTION [dbo].[TestSchema]

CREATE XML SCHEMA COLLECTION [dbo].[TestSchema] AS N'

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="TEST" elementFormDefault="qualified">

<xsd:element name="Root" type="xsd:string"/>

</xsd:schema>'

GO

DECLARE @.doc xml (TestSchema)

SET @.doc = ''

-- Inserting string of 64 characters

SET @.doc.modify('declare default element namespace "TEST";

insert <Root xmlns="TEST">123456789a123456789b123456789c123456789d123456789e123456789f1234</Root>

into (/)')

-- Inserting string of 70 characters

SET @.doc.modify('declare default element namespace "TEST";

insert <Root xmlns="TEST">123456789a123456789b123456789c123456789d123456789e123456789f1234567890</Root>

into (/)')

-- Inserting string of 10 characters

SET @.doc.modify('declare default element namespace "TEST";

insert <Root xmlns="TEST">123456789a</Root>

into (/)')

SELECT @.doc

Here is the result:

<Root xmlns="TEST">56789a123456789b123456789c123456789d123456789e123456789f12341234</Root>

<Root xmlns="TEST">56789a123456789b123456789c123456789d123456789e123456789f12341234567890</Root>

<Root xmlns="TEST">123456789a</Root>

You can see that first two strings are truncated of 4 characters at the start.

The problem occurs in case if:

1. The variable or column is typed XML.

2. Type of the string is xsd:string or derived.

3. The string is longer than 63 characters (no matter how much longer, what is truncated are alwasy first 4 characters).

Thanks a lot in advance!

This is known issue. We have fixed this bug in Yukon SP2.

Jinghao Liu

|||

Hello Jinghao,

Thanks for the prompt answer!

And do you know approximate term - when the SP2 is going to be released to public?

Best regards,

Yuriy

|||

You can ask your SQL support contact about the schedule of Yukon Service Pack 2. They usually know better than us about the date. If you are important customer, you might get the early version of it.

|||Thanks, we'll try to.

First 4 symbols of a string truncated when inserting typed XML

Dear SQL experts, is it a bug or I'm understanding something wrong?

Please look at the script below. Is it a bug? If yes, when can we expect it to be fixed and released? Are there any workarounds apart from just not using xsd:string type?

IF EXISTS (SELECT * FROM sys.xml_schema_collections c, sys.schemas s WHERE c.schema_id = s.schema_id AND (quotename(s.name) + '.' + quotename(c.name)) = N'[dbo].[TestSchema]')

DROP XML SCHEMA COLLECTION [dbo].[TestSchema]

CREATE XML SCHEMA COLLECTION [dbo].[TestSchema] AS N'

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="TEST" elementFormDefault="qualified">

<xsd:element name="Root" type="xsd:string"/>

</xsd:schema>'

GO

DECLARE @.doc xml (TestSchema)

SET @.doc = ''

-- Inserting string of 64 characters

SET @.doc.modify('declare default element namespace "TEST";

insert <Root xmlns="TEST">123456789a123456789b123456789c123456789d123456789e123456789f1234</Root>

into (/)')

-- Inserting string of 70 characters

SET @.doc.modify('declare default element namespace "TEST";

insert <Root xmlns="TEST">123456789a123456789b123456789c123456789d123456789e123456789f1234567890</Root>

into (/)')

-- Inserting string of 10 characters

SET @.doc.modify('declare default element namespace "TEST";

insert <Root xmlns="TEST">123456789a</Root>

into (/)')

SELECT @.doc

Here is the result:

<Root xmlns="TEST">56789a123456789b123456789c123456789d123456789e123456789f12341234</Root>

<Root xmlns="TEST">56789a123456789b123456789c123456789d123456789e123456789f12341234567890</Root>

<Root xmlns="TEST">123456789a</Root>

You can see that first two strings are truncated of 4 characters at the start.

The problem occurs in case if:

1. The variable or column is typed XML.

2. Type of the string is xsd:string or derived.

3. The string is longer than 63 characters (no matter how much longer, what is truncated are alwasy first 4 characters).

Thanks a lot in advance!

This is known issue. We have fixed this bug in Yukon SP2.

Jinghao Liu

|||

Hello Jinghao,

Thanks for the prompt answer!

And do you know approximate term - when the SP2 is going to be released to public?

Best regards,

Yuriy

|||

You can ask your SQL support contact about the schedule of Yukon Service Pack 2. They usually know better than us about the date. If you are important customer, you might get the early version of it.

|||Thanks, we'll try to.