Forum Replies Created

Viewing 15 posts - 1 through 15 (of 32 total)

  • RE: help with joining 2 tables

    exists is faster as many resources says.

    i tend to use exists not in.


    If something's hard to do, then it's not worth doing.

  • RE: help with joining 2 tables

    select * from table1 a

    where exists

    (select 1 from table2

    where table2.po# = a.po#)


    If something's hard to do, then it's not worth doing.

  • RE: Real Identity Value

    already figured it out

    thanks anyway


    If something's hard to do, then it's not worth doing.

  • RE: What is difference between != and operators ?

    as BOL they both have the same functionalities.

     

    they prevent (not always) the query optimizer from using an index to perform a search.

    i hear lot of thoughts about tu use...


    If something's hard to do, then it's not worth doing.

  • RE: varchar(max) disadvantages?

    ok seems enough for me

    what if i have sql server 2000

    i have to use Text datatype then

    what about Text dataype?


    If something's hard to do, then it's not worth doing.

  • RE: varchar(max) disadvantages?

    this field will be accessed frequently and very often

    select statement will be used often, insert as well

    less update and delete...


    If something's hard to do, then it's not worth doing.

  • RE: select query as function parameter

    thats the strict answer i was waiting

    10x


    If something's hard to do, then it's not worth doing.

  • RE: select query as function parameter

    yes john its the most clear way to do it

    i also did it

    but i was just wondering if a query can be written in the way i provided or its...


    If something's hard to do, then it's not worth doing.

  • RE: max row for each id

    for a specific ID i have one and only one max (ID)

     

    insert into @table

    select 1, 'A', '03/07/07' union all

    select 1, 'B', '09/07/07' union all

    select 1, 'C', '11/07/07' union all

    select 2,...


    If something's hard to do, then it's not worth doing.

  • RE: max row for each id

    10x for ur reply

    but i gave a simple example here

    the real case is that the row contains many fields , some are int, some are varchar....

    so i need that whole...


    If something's hard to do, then it's not worth doing.

  • RE: concatinate ids

    i use this:

     

    CREATE

    FUNCTION [dbo].[GetList]()

    RETURNS

    Varchar(20)


    If something's hard to do, then it's not worth doing.

  • RE: starting snapshot agent with replication script

    thanks noel for your help

    but i couldnt manage to get the snapshot job name from

    EXEC sp_MSenum_replication_agents @type = 1

    i tried to insert the result in a temp table but i...


    If something's hard to do, then it's not worth doing.

  • RE: Report execution error

    it happens when i try to run a report model


    If something's hard to do, then it's not worth doing.

  • RE: Distinct with no order

    @Charbel: this is never gonna happen unless you loop through your results and filter all doubles yourself! But that's probably not what you want to do.

     

    that wat i did and...


    If something's hard to do, then it's not worth doing.

  • RE: Distinct with no order

    i meant that the result are ordered after the distinct

    i want o get the results as they are in the table

    check the example i provided


    If something's hard to do, then it's not worth doing.

Viewing 15 posts - 1 through 15 (of 32 total)