SQL Server Select Query with and != condition Returns Strange Result [closed]












1















I have a table in a SQL Server database with 94 rows and when I try to fetch some particular rows using 



WHERE (EmpCode <> 001006)


it returns 63 rows instead of 93 rows. Please help



SELECT 

    ID, EmpID, EmpCode, EmpName, Designation, [Location], DoJ, Remarks, RoleID

FROM

    EmpDetails

WHERE

    (EmpCode <> 001006)

ORDER BY 

    EmpName





sql sql-server sql-server-2016







share|improve this question















closed as off-topic by GSerg, Mitch Wheat, Salman A, marc_s, Martin Smith Jan 1 at 11:50



  • This question does not appear to be about programming within the scope defined in the help center.

If this question can be reworded to fit the rules in the help center, please edit the question.

















  • if EmpCode is defined as a numeric column and it does not have a unique index, then it is possible to get this result.

    – NoChance
    Jan 1 at 7:46






  • 1





    @NoChance No chance.

    – GSerg
    Jan 1 at 7:48






  • 2





    Possible duplicate of Not equal <> != operator on NULL

    – GSerg
    Jan 1 at 7:49






  • 1





    I agree with @SalmanA. Another thing to consider is the fact that numbers do not have leading zeros, so 001006 is equal to 1006 and also to 0001006.

    – Zohar Peled
    Jan 1 at 8:23






  • 1





    @iminiki stackoverflow.com/q/18015422/11683

    – GSerg
    Jan 1 at 16:31
















1















I have a table in a SQL Server database with 94 rows and when I try to fetch some particular rows using 



WHERE (EmpCode <> 001006)


it returns 63 rows instead of 93 rows. Please help



SELECT 

    ID, EmpID, EmpCode, EmpName, Designation, [Location], DoJ, Remarks, RoleID

FROM

    EmpDetails

WHERE

    (EmpCode <> 001006)

ORDER BY 

    EmpName





sql sql-server sql-server-2016







share|improve this question















closed as off-topic by GSerg, Mitch Wheat, Salman A, marc_s, Martin Smith Jan 1 at 11:50



  • This question does not appear to be about programming within the scope defined in the help center.

If this question can be reworded to fit the rules in the help center, please edit the question.

















  • if EmpCode is defined as a numeric column and it does not have a unique index, then it is possible to get this result.

    – NoChance
    Jan 1 at 7:46






  • 1





    @NoChance No chance.

    – GSerg
    Jan 1 at 7:48






  • 2





    Possible duplicate of Not equal <> != operator on NULL

    – GSerg
    Jan 1 at 7:49






  • 1





    I agree with @SalmanA. Another thing to consider is the fact that numbers do not have leading zeros, so 001006 is equal to 1006 and also to 0001006.

    – Zohar Peled
    Jan 1 at 8:23






  • 1





    @iminiki stackoverflow.com/q/18015422/11683

    – GSerg
    Jan 1 at 16:31














1












1








1








I have a table in a SQL Server database with 94 rows and when I try to fetch some particular rows using 



WHERE (EmpCode <> 001006)


it returns 63 rows instead of 93 rows. Please help



SELECT 

    ID, EmpID, EmpCode, EmpName, Designation, [Location], DoJ, Remarks, RoleID

FROM

    EmpDetails

WHERE

    (EmpCode <> 001006)

ORDER BY 

    EmpName





sql sql-server sql-server-2016







share|improve this question
















I have a table in a SQL Server database with 94 rows and when I try to fetch some particular rows using 



WHERE (EmpCode <> 001006)


it returns 63 rows instead of 93 rows. Please help



SELECT 

    ID, EmpID, EmpCode, EmpName, Designation, [Location], DoJ, Remarks, RoleID

FROM

    EmpDetails

WHERE

    (EmpCode <> 001006)

ORDER BY 

    EmpName





sql sql-server sql-server-2016




sql sql-server sql-server-2016






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 1 at 12:49









iminiki

8091020




8091020










asked Jan 1 at 7:44









Ghaffar HunzaiGhaffar Hunzai

54




54




closed as off-topic by GSerg, Mitch Wheat, Salman A, marc_s, Martin Smith Jan 1 at 11:50



  • This question does not appear to be about programming within the scope defined in the help center.

If this question can be reworded to fit the rules in the help center, please edit the question.







closed as off-topic by GSerg, Mitch Wheat, Salman A, marc_s, Martin Smith Jan 1 at 11:50



  • This question does not appear to be about programming within the scope defined in the help center.

If this question can be reworded to fit the rules in the help center, please edit the question.













  • if EmpCode is defined as a numeric column and it does not have a unique index, then it is possible to get this result.

    – NoChance
    Jan 1 at 7:46






  • 1





    @NoChance No chance.

    – GSerg
    Jan 1 at 7:48






  • 2





    Possible duplicate of Not equal <> != operator on NULL

    – GSerg
    Jan 1 at 7:49






  • 1





    I agree with @SalmanA. Another thing to consider is the fact that numbers do not have leading zeros, so 001006 is equal to 1006 and also to 0001006.

    – Zohar Peled
    Jan 1 at 8:23






  • 1





    @iminiki stackoverflow.com/q/18015422/11683

    – GSerg
    Jan 1 at 16:31



















  • if EmpCode is defined as a numeric column and it does not have a unique index, then it is possible to get this result.

    – NoChance
    Jan 1 at 7:46






  • 1





    @NoChance No chance.

    – GSerg
    Jan 1 at 7:48






  • 2





    Possible duplicate of Not equal <> != operator on NULL

    – GSerg
    Jan 1 at 7:49






  • 1





    I agree with @SalmanA. Another thing to consider is the fact that numbers do not have leading zeros, so 001006 is equal to 1006 and also to 0001006.

    – Zohar Peled
    Jan 1 at 8:23






  • 1





    @iminiki stackoverflow.com/q/18015422/11683

    – GSerg
    Jan 1 at 16:31

















if EmpCode is defined as a numeric column and it does not have a unique index, then it is possible to get this result.

– NoChance
Jan 1 at 7:46





if EmpCode is defined as a numeric column and it does not have a unique index, then it is possible to get this result.

– NoChance
Jan 1 at 7:46




1




1





@NoChance No chance.

– GSerg
Jan 1 at 7:48





@NoChance No chance.

– GSerg
Jan 1 at 7:48




2




2





Possible duplicate of Not equal <> != operator on NULL

– GSerg
Jan 1 at 7:49





Possible duplicate of Not equal <> != operator on NULL

– GSerg
Jan 1 at 7:49




1




1





I agree with @SalmanA. Another thing to consider is the fact that numbers do not have leading zeros, so 001006 is equal to 1006 and also to 0001006.

– Zohar Peled
Jan 1 at 8:23





I agree with @SalmanA. Another thing to consider is the fact that numbers do not have leading zeros, so 001006 is equal to 1006 and also to 0001006.

– Zohar Peled
Jan 1 at 8:23




1




1





@iminiki stackoverflow.com/q/18015422/11683

– GSerg
Jan 1 at 16:31





@iminiki stackoverflow.com/q/18015422/11683

– GSerg
Jan 1 at 16:31












1 Answer
1






active

oldest

votes


















0














If EmpCode is a varchar datatype you should type:



WHERE (EmpCode <> '001006')


If you also want to fetch null values, you should type:



WHERE (EmpCode <> '001006') OR (EmpCode IS NULL)





share|improve this answer
































    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    If EmpCode is a varchar datatype you should type:



    WHERE (EmpCode <> '001006')


    If you also want to fetch null values, you should type:



    WHERE (EmpCode <> '001006') OR (EmpCode IS NULL)





    share|improve this answer






























      0














      If EmpCode is a varchar datatype you should type:



      WHERE (EmpCode <> '001006')


      If you also want to fetch null values, you should type:



      WHERE (EmpCode <> '001006') OR (EmpCode IS NULL)





      share|improve this answer




























        0












        0








        0







        If EmpCode is a varchar datatype you should type:



        WHERE (EmpCode <> '001006')


        If you also want to fetch null values, you should type:



        WHERE (EmpCode <> '001006') OR (EmpCode IS NULL)





        share|improve this answer















        If EmpCode is a varchar datatype you should type:



        WHERE (EmpCode <> '001006')


        If you also want to fetch null values, you should type:



        WHERE (EmpCode <> '001006') OR (EmpCode IS NULL)






        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Jan 1 at 11:44









        Amessihel

        2,3891724




        2,3891724










        answered Jan 1 at 11:35









        PeibolPeibol

        13




        13

















            -

            Popular posts from this blog

            Monofisismo

            Image
            Monofisismo (do grego: monos - "único, singular" e physis - "natureza") é o ponto de vista cristológico que defende que, depois da união do divino e do humano na encarnação histórica, Jesus Cristo, como encarnação do Filho ou Verbo ( Logos ) de Deus, teria apenas uma única "natureza", a divina, e não uma síntese de ambas. O monofisismo é contraposto pelo diofisismo (ou "diafisismo"), que defende que Jesus preservou em si as duas naturezas. Historicamente, o monofisismo se refere primordialmente à posição dos que (especialmente no Egito e, em menor grau, na Síria) rejeitaram as decisões do Concílio de Calcedônia em 451 (o quarto concílio ecumênico). Os membros mais moderados entre eles, porém, defendem a teologia "miafisita", que se tornou a oficial para as Igrejas Ortodoxas Orientais. Muitos ortodoxos orientais, porém, rejeitam essa classificação, mesmo como um termo genérico, mas ele é amplamente utilizado na literatura históri
            Read more

            Angular Downloading a file using contenturl with Basic Authentication

            Image
            0 I have a contentUrl when user clicks on that,file should be downloaded. If I try to browse the contentUrl in the browser it asks for Userid and password.I believe this is Basic Authentication.I dont want user to enter UserId and Password so I am passing it Authorization(Please see below code). Url looks some thing like this: http://XXX.XXX.XX.XXX:8080/flowable-rest/service/runtime/tasks/90875/attachments/90555/content let username : string = 'admin'; let pwd : string = 'test'; let headers = new Headers(); headers.set('Accept', 'text/json'); headers.append('Content-Type', 'application/json'); headers.set('Access-Control-Allow-Origin', '*'); headers.set('Access-Control-Allow-Methods','POST, GET, OPTIONS, PUT, DELETE'); head
            Read more

            Olmecas

            Image
            Monumento 1, uma das quatro cabeças colossais encontradas em La Venta, com altura aproximada de 3 metros Olmecas é a designação do povo e da civilização que estiveram na origem da antiga cultura pré-colombiana da Mesoamérica e que se desenvolveram nas regiões tropicais do centro-sul do atual México durante o pré-clássico, próximo de onde hoje estão localizados os estados mexicanos de Veracruz e Tabasco, no Istmo de Tehuantepec, numa zona designada área nuclear olmeca. A cultura olmeca floresceu nesta região aproximadamente entre 1500 e 400 a.C., [ 1 ] e crê-se que tenha sido a civilização-mãe de todas as civilizações mesoamericanas que se desenvolveram posteriormente. [ 2 ] No entanto, desconhece-se a sua exacta filiação étnica, ainda que existam numerosas hipóteses colocadas para tentar resolver esta questão. O etnónimo olmeca foi cunhado pelos arqueólogos do século XX, e não devem confundir-se com os muito posteriores olmecas-xicalancas que ocuparam vários locais do México
            Read more