Forum Replies Created

Viewing 15 posts - 1,666 through 1,680 (of 2,496 total)

  • RE: clustered index

    The approach to clustering is different between SQL Server and DB2.

    As most SQL people know, SQL Server will always physically insert a new row in the correct place in a...

  • RE: clustered index

    The description I gave about MDC was very simplified. If you want more details then you have to search the DB2 documentation.

    Believe me, MDC does what it says on...

  • RE: clustered index

    I really don't see any way to have multiple clustered indices without storing multiple copies of the data, as it's not clustered unless it's physically stored in that order.

    In DB2,...

  • RE: Database becomes unavailable in SQL Server 2005

    You get this message when the database files are closed.

    Having AUTOCLOSE on is the commonest way that database files get closed, but there are others...

    ALTER DATABASE xxx SET OFFLINE

    ALTER...

  • RE: CLR out of memory

    The OP said there was plenty of memory on the box.

    Remember that with 32-bit SQL Server, the ONLY thing that can use memory above the 4GB line is...

  • RE: clustered index

    A clustered index physically stores the data in the sequence given in the index definition. The way this is implemented in SQL Server means you can only have 1...

  • RE: 64GB RAM on SQL 2005 Standard on W2K3 Enterprise

    They exist, but you do not have to adjust them. Changes to these are only needed if you have specific requirements that could be met by using affinity masks.

  • RE: 64GB RAM on SQL 2005 Standard on W2K3 Enterprise

    There are a few threads on this forum that have focussed on the differences between 32-bit and 64-bit SQL Server 2005. Most people would not hit any issues, but...

  • RE: 64GB RAM on SQL 2005 Standard on W2K3 Enterprise

    If the only thing running on your box is the OS and SQL server, than setting max memory to 62 GB might just work, sometimes.

    If you run anything else (anti-virus,...

  • RE: Reinstalling SQL Server 2005

    I would say that 2 hours to uninstall and reinstall SQL 2005 is good! I find that the uninstall can easily take 40 minutes, and the install along with...

  • RE: Reinstalling SQL Server 2005

    If you aer re-installing to the same folders, there is no need to delete them between the uninstall and the new install.

    You should not restore any other system databases apart...

  • RE: Getting the excessive paging error

    Windows want to use more memory than it has available.

    As Chirag says, check what is happening in SQL Server. SQL should adjust its memory use to avoid excessive paging,...

  • RE: SQL Server 2005 max memory and /3GB switch

    In 32-bit mode, SQL Server 2005 SE can use AWE along with Windows /PAE switch to use memory above the 4 GB line.

    Only the buffer cache can use memory above...

  • RE: DTS packages SQL Server 200

    SqlServerFineBuild is free, but you can make a contribution (it goes direct to charity) if you wish.

  • RE: Database File Size

    There are 2 issues - SQL table & index fragmentation, and NTFS disk fragmentation.

    To reduce the size of your database, I would look at a) delete the unwanted data, b)...

Viewing 15 posts - 1,666 through 1,680 (of 2,496 total)