Forum Replies Created

Viewing 15 posts - 706 through 720 (of 1,518 total)

  • RE: "Scale-out deployment" error while migrating Reporting Services from SQL 2005 to SQL 2008

    Gift Peddie (2/6/2009)

    Scale out error means you are running either SQL Server Express or Standard and is trying to deploy reports created in either Enterprise or Developer edition.

    The short answer...

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

    February 6, 2009 at 9:06 am

    #939608

  • RE: "Scale-out deployment" error while migrating Reporting Services from SQL 2005 to SQL 2008

    I should point out that I am migrating from SQL-2005 Enterprise Edition to SQL-2008 Standard Edition.

    In the Reporting Services Configuration Manager for SQL 2008 I have removed the entries in...

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

    February 6, 2009 at 8:36 am

    #939585

  • RE: SCOM 2007 SP1 and SQL 2008

    MarkusB (2/4/2009)

    Marios Philippopoulos (2/3/2009)

    Can System Center Operations Manager 2007 SP1 monitor SQL 2008 instances?

    Yes, it can. There is a management pack for SQL Server which supports SQQL 2000,2005 and 2008.

    http://technet.microsoft.com/en-us/opsmgr/cc539535.aspx

    Thank...

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

    February 4, 2009 at 7:41 am

    #937965

  • RE: Costly update trigger -70,000,000 logical reads for 30,000 rows updated!

    TheSQLGuru (2/3/2009)

    Marios Philippopoulos (1/31/2009)

    I have a trigger that appears to execute a very large number of logical reads; on one occasion it has hit 73,421,728 logical reads!

    There are two puzzling...

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

    February 3, 2009 at 8:47 am

    #937193

  • RE: Costly update trigger -70,000,000 logical reads for 30,000 rows updated!

    Here is the "actual" exec plan obtained from a server-side trace (see attached).

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

    February 3, 2009 at 4:24 am

    #937009

  • RE: Costly update trigger -70,000,000 logical reads for 30,000 rows updated!

    TheSQLGuru (2/2/2009)

    Other than the ol' trigger-firing-itself-due-to-update-inside-trigger-ploy, 2 other questions:

    1) any OTHER triggers on this table?

    2) is the join column a primary key or unique index value? Looks like...

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

    February 2, 2009 at 1:10 pm

    #936697

  • RE: Costly update trigger -70,000,000 logical reads for 30,000 rows updated!

    GilaMonster (2/2/2009)

    Nested triggers means that an update to a table in a trigger can fire triggers on that table, providing it's not the same table. So, say you have Table1...

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

    February 2, 2009 at 10:59 am

    #936596

  • RE: Costly update trigger -70,000,000 logical reads for 30,000 rows updated!

    GilaMonster (2/2/2009)

    Marios Philippopoulos (2/2/2009)

    Wow, would the trigger feed on itself that way? I hadn't thought of that...

    That's only possible if recursive triggers are enabled. It's a database-level option and it's...

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

    February 2, 2009 at 10:48 am

    #936581

  • RE: Monitoring Database Blocking Through SCOM 2007 Custom Rules and Alerts

    Harold Buckner (2/2/2009)

    Marios

    I was doing some more thinking on this script....and thought......

    Currently the alert is generated from the managed server and the computer name in the event is the managed...

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

    February 2, 2009 at 8:50 am

    #936481

  • RE: Costly update trigger -70,000,000 logical reads for 30,000 rows updated!

    Peso (2/2/2009)

    The trigger is updating the same base table on where the trigger is resided.

    So when the trigger updates the two columns, the same trigger is fired again!

    And again.. And...

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

    February 2, 2009 at 8:45 am

    #936474

  • RE: Costly update trigger -70,000,000 logical reads for 30,000 rows updated!

    Peso (2/2/2009)

    No need to check for UPDATE, DELETE or INSERT.

    Trigger is designed for UPDATE.

    Also, the trigger is nesting itself by updating the table for which the trigger ís triggering on...

    Use...

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

    February 2, 2009 at 8:22 am

    #936463

  • RE: Costly update trigger -70,000,000 logical reads for 30,000 rows updated!

    GilaMonster (2/2/2009)

    Marios Philippopoulos (2/2/2009)

    Wow, that was something I didn't know, but makes sense the way you put it.

    Not that I don't believe you, but can you post a link that...

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

    February 2, 2009 at 7:57 am

    #936443

  • RE: Is my clustered index in need of a rebuild?

    Grant Fritchey (2/2/2009)

    Every system is different, but I personally wouldn't sweat fragmentation until it at least got as high as 20% and probably I wouldn't do a rebuild until I...

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

    February 2, 2009 at 7:51 am

    #936435

  • RE: Costly update trigger -70,000,000 logical reads for 30,000 rows updated!

    GilaMonster (2/1/2009)

    RBarryYoung (2/1/2009)

    But Marios should be able to get the Actual from Profiler or tracing, right?

    Yes, absolutely. Providing he traces the correct event. I seem to recall there are about...

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

    February 2, 2009 at 4:24 am

    #936331

  • RE: Costly update trigger -70,000,000 logical reads for 30,000 rows updated!

    GilaMonster (2/1/2009)

    Marios Philippopoulos (2/1/2009)

    I don't think it's the estimated exec plan, I obtained it from sys.dm_db_exec_requests. It was retrieved when the statement was actually executed...

    It's the same as the 'estimated'...

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

    February 2, 2009 at 4:22 am

    #936329

Viewing 15 posts - 706 through 720 (of 1,518 total)