Viewing 15 posts - 391 through 405 (of 3,232 total)
CirquedeSQLeil (7/19/2010)
John Rowan (7/19/2010)
tosscrosby (7/16/2010)
lumbricus terrestris can be a money-maker, depending on where you live...
I'm in the mid-west. They would make money here. I'll be adding...
July 19, 2010 at 1:38 pm
tosscrosby (7/16/2010)
lumbricus terrestris can be a money-maker, depending on where you live...
I'm in the mid-west. They would make money here. I'll be adding that to my...
July 19, 2010 at 12:28 pm
Zophobas morio
(not so random worm - my next project is to breed them for pet consumption)
July 16, 2010 at 9:53 am
I'm glad you figured it out. I would still suggest that you take steps to make your data types consistent accross your tables.
July 16, 2010 at 9:42 am
Here's how I've done it.
1. Create a Data Flow task.
2. Inside Data flow, use OLE DB Source adapter to get your XML. I use a stored procedure. I...
July 15, 2010 at 1:06 pm
--==== Build test table
DECLARE @Table TABLE (
RowID int IDENTITY(1,1) NOT NULL PRIMARY KEY,
DecimalValue decimal(18,2) NOT NULL
)
--==== Insert test data into table
INSERT INTO @Table(DecimalValue)
SELECT 2316842 UNION ALL
SELECT 594649871 UNION ALL
SELECT...
July 12, 2010 at 3:00 pm
Comparing 123 accross those data types should evaluate to an equality. Are you seeing something different.
On another note, you may want to correct the problem of storing the same...
July 12, 2010 at 2:33 pm
Nope, it will round the incoming data to fulfill the datatype, but not change the #.
July 12, 2010 at 2:31 pm
That's because 124757266 is a whole number. If your number was 1247572.66156413, then you'd get 1247572.66.
If you want to add a decimal point, divide it by 100.
INSERT INTO...
July 12, 2010 at 2:12 pm
Viewing 15 posts - 391 through 405 (of 3,232 total)