Forum Replies Created

Viewing 15 posts - 48,256 through 48,270 (of 49,571 total)

  • RE: UPDATA STATISTICS

    -- For SQL 2005

    SELECT STATS_DATE(object_id, index_id), object_name(object_id)

    from sys.indexes where object_id = object_id('TableNameHere')

    Edit: Just noticed your on SQL 2000....

    Not exactly the same, cause of the changes to the system...

  • RE: Regarding triggers on a table

    Look up sp_helptrigger in Books Online

  • RE: impact of "permanent" sql trace on production server?

    emamet (11/9/2007)


    Yes, I was planning to select very few events and columns as well as putting a filter on duration.

    When you set up your filter, remember that durations are measures...

  • RE: impact of "permanent" sql trace on production server?

    Agreed. Don't use the profiler GUI when tracing against production servers. The server-side trace procs are a much better idea.

    Basically, you don't want to be sending the trace info across...

  • RE: Tale of <> Operator

    You're correct on what a cartesian product is.

    Jeff was asking how an OR used in a where clause will get you a cartesian product.

  • RE: Performance related queries

    You'll probably get better and more accurate advice if you read up on the concepts in Books Online and on the MSDN pages, then post here for specifics that aren't...

  • RE: jobs running uder same SPID causing Temp table problems

    Spids get reused. If your job completes and disconnects, another job connects a second later, there's a chance of it running under the same SPID as the first job. It...

  • RE: keep track of SQL Statement

    Since you're on SQL 2005, you can use one of the DMVs to retreive tha last statement executed, instead of InputBuffer that only returns 255 characters

    SELECT er.session_id, blocking_session_id, wait_type, wait_time,...

  • RE: impact of "permanent" sql trace on production server?

    Depends on your server and the activity. If you do set up a permanent trace there are a few things to be careful of.

    1 - Don't trace the very high...

  • RE: Reporting Tables (Denormalize tables)

    While you can have rows of a size larger than 8060 bytes in SQL 2005, they should still be avoided.

    The page size hasn't changed and the largets row that...

  • RE: is there any difference between != and <>

    Jeff Moden (11/7/2007)


    Sounds strange, but I can always tell who wrote the code if != is used... some Java programmer 😉

    😀 I always use !=, but I'm not...

  • RE: Performance related queries

    This smells of homework, or interview questions. Is that the case?

    Most of tthese are easily answered with Books online or a quick google search

    karthikeyan (11/7/2007)


    Hi Experts,

    1. Tell me the difference...

  • RE: Table locks resulting from trigger

    That's not inserting into the table with the insert trigger. The trigger is on dbo.OEORDH, and that insert inserts into dbo.Derived_DB.tbl_ORDERS (a very, very strange table name. The database is...

  • RE: How to make audit trigger 'capture' all rows affected?

    Depends on the business requirements. In one of the systems I maintain, we have to (for legal purposes) have a record of who inserted the rows and when (along with...

  • RE: Tale of <> Operator

    Depends on the query and what you're trying to achieve.

    FRom what I read of the article you linked to, the advice isn't to not use the inequality ever, but to...

Viewing 15 posts - 48,256 through 48,270 (of 49,571 total)