Forum Replies Created

Viewing 15 posts - 166 through 180 (of 283 total)

  • RE: float vs int

    So if i move to Big int data type then will there be performance improvement?

    here i am mainly concern about data reading(Select).

  • RE: float vs int

    twin.devil (3/10/2014)


    when you say performance... what exactly you are referring to? do you want this column to be primary key as well ?

    No. I dont wnat this column to be...

  • RE: float vs int

    Koen Verbeeck (3/10/2014)


    If you are not going to store decimal values (and also not in the future), I see no reason to choose float.

    Go with int.

    Yes for sure i am...

  • RE: Migrate GUID TO BIGINT

    As i said since the data is growing large and large having uniqueidentifier and querying the data might takes time.

    Inorder to reduce the time in future to insert the data...

  • RE: Migrate GUID TO BIGINT

    Yet to test process, before that getting into the process,ensuring that the process which i have followed is ok or need to modify.

    Next thing is can we hold GUID itself...

  • RE: Insert is Slow

    In general it will be a bit faster because a guid is 16 bytes where a bigint is only 8 bytes. It is not likely to make a huge difference.

    You...

  • RE: Insert is Slow

    Thanks Sean!

    I got it we should not go with cluster index for guid since this will cause physical ordering of the data on the disk which is pointless one.

    One more...

  • RE: Insert is Slow

    I think you are inserting data into TableA which has a uniqueidentifier as the clustered index? That is source of your problem. The index fragmentation is going to be through...

  • RE: Insert is Slow

    As i said

    TableA C1 uniqueidentifier (PK), C2 uniqueidentifier, C3 ......

    PK is a cluster index

    TableB C1 uniqueidentifier(PK) , C2 uniqueidentifier (FK_TableA_uniqueidentifier ), C3 ......

    Column c1 PK is a cluster index and...

  • RE: Migrate SQL 2000 to 2008

    Plan to get a new server for SQL2008 and migrating the dbs to it.

    Main concern over the migration is performance improvement.

    We are using 4gb of RAM for the current client,...

  • RE: Improve performance

    Hi EricEyster,

    After having bacth operation is delete operation faster?

    how much time you gained after rewritting your query.

    Incase what if in lower version of sql server say sql server 2000 how...

  • RE: Is cascade delete Slow

    So u mean to say

    Delete from main_table where id=some_input;

    Delete from Child_table1 where id=some_input;

    Delete from Child_table2 where id=some_input;

    Delete from Child_table3 where id=some_input;

    Commit tran;

  • RE: Improve performance

    So steve you are suggesting some thing like

    EXEC ('DELETE Top (10000) FROM '+ @Table_Name +' WHERE RUN_START_TIME<=' + @pdate + '')

    COMMIT TRAN

    DELETE Top (10000) TESTDATA WHERE RUN_START_TIME...

  • RE: Is cascade delete Slow

    Grant Fritchey (3/5/2014)


    Cascade delete is pretty dangerous. I don't know of many people that use it. It tends to create very large transactions that lead to lots and lots of...

  • RE: Migrate SQL 2000 to 2008

    Steve Jones - SSC Editor (3/3/2014)


    One big thing would be to move to a stable x64 platform. That was an add-on in SQL 2000, but in SQL2K8 you can easily...

Viewing 15 posts - 166 through 180 (of 283 total)