Viewing 15 posts - 76 through 90 (of 109 total)
I *can* read Garadin. That is why I was questioning the above statement. Seems to me that defining a #table would be more use, as you can use it...
December 8, 2009 at 7:07 pm
Seriously? You can only use a CTE in the statement immediately following?
When I read the article, the impression I got was that you could define a CTE at the...
December 8, 2009 at 6:23 pm
I found the answer - use a conditional split - work out which column can never be null for a valid row, divert all of the rows that do NOT...
October 21, 2009 at 4:11 pm
And by embracing the usage of technology, I should get the first reply in here...and I'm 48 (baby boomer)
September 29, 2009 at 11:59 pm
Each to their own - personally I can't see why being able to store values from zero to 255 is a better way of storing a boolean field than what...
September 23, 2009 at 8:37 pm
Actually, I'm asking why certain data types throw an error when you try to assign a larger value to it, and other times it doesn't - and why variables are...
September 23, 2009 at 8:22 pm
Yes - but we are using BIT fields, not Int.
September 23, 2009 at 8:09 pm
Matt - thanks for that. -1 is still more than a bit field, as it takes 8 bits (I think) to store it, whereas 0 & 1 only...
September 23, 2009 at 5:45 pm
Matt - bit fields are either 1 or 0, not -1 - that's all they can be, as there is only one "bit" to hold the value and binary is...
September 23, 2009 at 4:39 pm
Yes - I also got that as well, however neither -1 or 66 shoudl fit into a bit field, which *should* be only zero or one. Interesting...
September 22, 2009 at 6:46 pm
Is the "About" page correct?
Steve Jones is editor-in-chief of SQLServerCentral.com. Steve started working with SQL Server in 1991 with the original Sybase port of SQL Server to OS/2 v1.3 (shudder)....
September 22, 2009 at 4:13 pm
Create a variable in your package (intID)
In your script
Dts.Variables("intID").Value = Cint(Dts.Variables("intID").Value) + 1 ' or however else you want to manipulate it.
July 8, 2009 at 4:44 pm
Once you've created the destination file, uncheck the "column names in the first row" for the source file.
July 8, 2009 at 3:45 pm
Once you've created the destination file, uncheck the "column names in the first row" for the source file.
July 8, 2009 at 3:44 pm
Seems a bit silly to have a transaction that doesn't apply to table variables - I think I'll have to go and read MSDN to find out a bit more!
Great...
July 7, 2009 at 4:04 pm
Viewing 15 posts - 76 through 90 (of 109 total)