Forum Replies Created

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

  • RE: Index scan results in "Too complex query" error

    Oh dear. Oh dear dear. Such an idiot I am.

    There are several thousand(!) FOREIGN KEYS to this table from several thousand other tables. With cascade delete.

    The server tries to delete...

  • RE: Getting sporadic "severe error" on 2008 R2 SP2 instance

    Today I know MUCH more.

    The problem arises when Replication agents start from their schedules. It never arises if I start the same agents from the Replication Monitor or 'View synchronization...

  • RE: Getting sporadic "severe error" on 2008 R2 SP2 instance

    RTaylor2208 (2/19/2013)


    Is there any errors reported in the SQL Server Error log within management in SSMS

    No.

    or any errors written to the windows event logs?

    No. Or I do not see any.

  • RE: How much data have you replicated with Transactional Replication?

    KTD (2/11/2013)... replicating a large DB of this size.

    Not of this size. 15 times smaller... but this looks like irrelevant. The using of snapshot was out of question from the...

  • RE: Could the disconnected database be updated?

    anthony.green (2/12/2013)


    Replicate into another database on ServerA the data that you want to send.

    Back it up, send it to ServerG for ServerB to see, then do regular transaction log backups...

  • RE: what is Scalability of Database

    Subbu's (1/11/2013)


    What is scalability of a database.

    For the first approximation "scalability" is an ability to scale ;).

    It means the ability to deal with increased workload just by adding more hardware...

  • RE: Why the table can only have one clustered index?

    Dave Ballantyne (12/29/2012)


    From a conceptual point of view think of this:

    In a phone directory the clustered index is LastName,FirstName, Street Address.

    That being the case how can the be a clustered...

  • RE: Why the table can only have one clustered index?

    GilaMonster (12/29/2012)


    Because the table only exists once.

    Gail, this is just the question. I know how the things are - I do not understand why. The table only exists once...

  • RE: Aggregates in T-SQL

    Lokesh Vij (12/21/2012)

    I do not agree with this. COUNT(*) only considers counting the number of rows. It does not even bother to take a look at the columns and there...

  • RE: Aggregates in T-SQL

    There is just one variant of one aggregate function that DOES take nulls into account: COUNT(*).

    However, it is uncompatible with DISTINCT clause.

    SELECT COUNT(col1) as cnt_col1

    ,...

  • RE: UNIQUE constraint

    SQLRNNR (12/20/2012)


    I don't disagree with the correct answer. I disagree with the explanation. I also do disagree with many of the complaints thus far about the question. ...

  • RE: ORDER BY Should be same as my input in IN()

    Jeff Moden (12/19/2012)

    One is that it's SQL Server proprietary and will not port to most other RDBMS engines.

    Another reason is that it will allow you to make mistakes (just like...

  • RE: UNIQUE constraint

    Lokesh Vij (12/19/2012) Ideally, both Unique constraint and Unique index are same as Unique Constraint creates Unique Index to maintain the constraint to prevent duplicate keys.

    They are definitely not. Every...

  • RE: UNIQUE constraint

    Do not like the question.

    First of all, it IS definitely possible to create a table which would accept any number of NULLs but no duplicate non-null values in 2005 and...

  • RE: ORDER BY Should be same as my input in IN()

    - Used UPDATE...FROM more than once

    I definitely do not have the slightest resembalnce to "SQL Expert", but this phrase punched me hard.

    I have no idea why using UPDATE...FROM is bad....

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