Forum Replies Created

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

  • RE: Query too slow

    I added full text index on the DESCRIPTION column and ran the query. It did not improve the performance.

    I believe syntax is also different from the query while using...

  • RE: Query too slow

    The reason, Incident Description is not included in index is that it is ntext data type.

  • RE: Query too slow

    As far as why we require the other fields in the query just to get the count, I have sent this question to the developers since this query is being...

  • RE: Query too slow

    I ran this query that was mentioned earlier in the one of the responses

    SELECT count(*)FROM [MAGICSSHD].[Incident] WITH (NOLOCK)WHERE [State:] = N'C'...

  • RE: Query too slow

    Here is the view that the query is retrieving from. The earlier script is from DDL of the table that this view is using

    CREATE view "MAGICSSHD"."Incident" AS SELECT...

  • RE: Query too slow

    Here is the DDL script for the table in the customer's database that they have customized.

    CREATE TABLE [_SMDBA_].[_TELMASTE_] (

    [SEQUENCE] [int] NOT NULL ,

    [LASTMODIFIED] [datetime] NOT NULL ,

    [LASTUSER] [nvarchar] (30) NULL...

  • RE: Permissions issue

    Thanks for the reply.  I found out that just now.  Do you think this has been changed in SQL 2005.

  • RE: export data from every table

    Thanks for the script to use BCP.  Will this script handle if the table's data has non-english data as well?

  • RE: export data from every table

    I have trying to avoid scripting all the triggers if I have to go this route.  I could give it a try.

    For char & varchar, I run Alter table Alter...

  • RE: export data from every table

    I don't know if SQL Server will be able to handle all the columns at one time, since I will have lot of text columns and it might need lot...

  • RE: export data from every table

    I want to reinsert it using DTS as well.

    The reason I want to do this, as part of our upgrade, we are making our product's table unicode friendly, which means...

  • RE: Deadlocking issue

    Here is what we are seeing.

    We have Table1 with Col1,Col2,Col3,Col4.

    In the update trigger of the Table1, we have update statement to update Col2 = getdate() for the updated record.

  • RE: Deadlocking issue

    It gets executed

  • RE: Results of a procedure into a cursor

    Thanks for the reply.  That is what I intended to do if I had no solution for this one.

  • RE: sysusers table

    The only reason for now, I want to use this view is that, our product still supports SQL 2000 and SQL 2005.  I do not want to maintain 2 sets...

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