Forum Replies Created

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

  • RE: Update with Inner Join

    yes thats correct but i want to do multiple ones at the same time, i.e. hong kong, singapore, monaco. these are all stored in the joining table but still not...

  • RE: Update with Inner Join

    but even with the joining table de-duped it still produces the same count. Does it matter if the original table i am trying to update to NULL has dupes? i.e....

  • RE: Update with Inner Join

    ok i will select distinct from that table and create a new table and then use that one.

    Thanks for all your help

  • RE: Update with Inner Join

    oh ok, so if if de-dupe my connecting table then it should update fine?

  • RE: Update with Inner Join

    so are you saying my update statement will never update what i want to (i.e. the select statement)

  • RE: Update with Inner Join

    ok i have dupes in the staging table but surely this should not matter, when it sees Singapore in the staging table and in the update table then it should...

  • RE: Update with Inner Join

    yes they are im afraid

  • RE: Update with Inner Join

    thanks for this, but both of the statement run fine but i am gaining different results when i am expecting the same number of records

  • RE: Bulk Excel Imports

    ok, i do know a lil SSIS but what flow items do i use?

  • RE: Bulk Excel Imports

    at the moment, through import data tool i can only import a file one by one but i would like to do all at once so i dont to do...

  • RE: Multi Part identifier could not be bound

    well thanks for all of your replies but i have just started using sql so am a little rusty on the syntax ect.

  • RE: Violation of PRIMARY KEY constraint

    yes pretty much meaningless, what does that statement actually do though?

    'id' does mean something but i have 2 tables with results in that i want to amalgamate but they both...

  • RE: Violation of PRIMARY KEY constraint

    please see my posts above, i do not want duplicates but need to set the id sequential starting from 1000000

  • RE: Violation of PRIMARY KEY constraint

    i used this code to do this:

    DECLARE @SourceID INT;

    DECLARE @Counter INT;

    SET @Counter = 1;

    DECLARE ins_accounts CURSOR

    FOR

    SELECT id FROM attributes

    OPEN ins_accounts

    FETCH NEXT FROM ins_accounts

    INTO @SourceId

    WHILE @@FETCH_STATUS = 0

    BEGIN

    ...

  • RE: Violation of PRIMARY KEY constraint

    yes this is correct; so how do i make the id sequential starting from 1000000? so i do not have any duplicates

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