Forum Replies Created

Viewing 15 posts - 16 through 30 (of 34 total)

  • RE: HASHBYTES can help quickly load a Data Warehouse

    bohra_anand (4/15/2010)


    I am getting this error

    Msg 156, Level 15, State 1, Line 1

    Incorrect syntax near the keyword 'as'.

    Msg 156, Level 15, State 1, Line 3

    Incorrect syntax near the keyword...

  • RE: Hello SSIS World, From XML!

    Stan Kulp-439977 (4/15/2010)


    I just meant this as an introduction, thus the "Hello World" allusion.

    Agreed, but using a recordset/foreach loop and a script task is not quite "hello world" material. ...

  • RE: HASHBYTES can help quickly load a Data Warehouse

    Mike C (4/14/2010)


    So yes, you are correct, once you've generated 1,208,925,819,614,629,174,706,176 160-bit hashes in a single table you're fairly certain to have a collision and it's probably time to move...

  • RE: NULL

    mtillman-921105 (4/13/2010) OK, fair enough. Then how do you handle the nulls in your numeric fields where you want to add and you want the nulls to = 0?...

  • RE: NULL

    Hugo Kornelis (4/13/2010)


    mtillman-921105 (4/13/2010)


    But I still wish that SQL would use it as a zero since in the real world when we add 5 + NULL we want to see...

  • RE: NULL

    Errr, how do I get my point back? NULL does not mean anything. "Absence of any value" - hence it cannot mean "unknown." The answer choice "NULL"...

  • RE: Hello SSIS World, From XML!

    Why was this not done entirely in the data flow, where batch inserts could be done, as opposed to row-by-row in your method? You can use a data viewer...

  • RE: Preventing usage of "SELECT *..."

    paul.knibbs (1/11/2010)


    I believe I made that comment, and it was not ever intended to say that SELECT * should be removed--as you rightly say, it is a useful development tool....

  • RE: Preventing usage of "SELECT *..."

    SQL Noob (11/5/2009)

    isn't that going to be caught in testing?

    when we were getting ready for sql 2005 we found our developers had written code that looks like

    select column1, column1...

  • RE: Preventing usage of "SELECT *..."

    djnewman (11/5/2009)


    OK, but what about Exists clauses? We need to use select * from in at least some of those cases (yes I know about null and 1 and whatever,...

  • RE: Preventing usage of "SELECT *..."

    Peter_Beery (11/5/2009)


    I would imagine that most organizations have folks doing purely business research/analytical work on their data in their databases. While I agree that select * ... isn't appropriate for...

  • RE: Preventing usage of "SELECT *..."

    The problem with this approach is that the user can no longer do COUNT(*) as was indicated.

    COUNTing a column, especially one that allows NULLs (perhaps a unique non-null primary key...

  • RE: Using SSIS to Capture the File Name

    A Joy (10/6/2009)


    This article should probably specify it only works 'as is' with VS2005.

    There are a number of variances in VS2008

    The ForEachLoopEditor requires some additional steps and the .net script...

  • RE: Using SSIS to Capture the File Name

    J.D. Gonzalez (10/5/2009)


    This is great feedback. It's actually a philosophical discussion here at the office. My personal reason for not just grabbing the file name only is that...

  • RE: Using SSIS to Capture the File Name

    Peso-284236 (10/5/2009)


    For the first part, isn't it just easier to use the "FileName" property of load-component?

    Yes, indeed. My thoughts exactly. The problem with this write-up is that there...

Viewing 15 posts - 16 through 30 (of 34 total)