Forum Replies Created

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

  • RE: Use Backup/Restore to Minimize Upgrade Downtimes

    I have used this method for years. Even with busy and/or large databases, I can move a database server to a new piece of hardware with only about 10 minutes...

  • RE: Moving Databases

    SQL 2005? 2000?

    Are master and the other system databases going to have the same drive letter/path on the new box?

    If so, it should be fairly straightforward. Start SQL Server in...

  • RE: Moving Databases

    Standard drive letters are nice. But, one place that you are forced use different letter is on Microsoft Cluster Services clusters. Each instance on a cluster must have its own...

  • RE: Lookup Table Design

    Why can the user preferred names be saved in the database with the 'official' versions of the names? Why would you trust a number of GUI's to translate everything consistently?

    You...

  • RE: Lookup Table Design

    I am trying to understand the point of letting the GUI do the translating.

    For instance, I have a database that contains the transactional data for one of the systems...

  • RE: Lookup Table Design

    roger clarke (10/19/2007)


    The meaning of a code is entirely subjective

    If you have a code WHS123 that is a 'local distribution warehouse', it may have many translations into local languages, but...

  • RE: Lookup Table Design

    Why wouldn't you place the language translations in tables?

    Do you really trust that every application running against your database is going to decoding correctly? For the same reasons, you would...

  • RE: Starting and Stopping SQL Server Part 1

    Each instance has a unique service name. Named instances are named something like MSSQL$MyInst.

    So, just run NET START MSSQL$MyInst from the command line.

  • RE: The Challenge: Litespeed v TDPSQL

    My LiteSpeed backup and restores are at least three times faster than the equivalent native operations were.

  • RE: Lookup Table Design

    This is one of the worst practices from design and performance standpoints.

    First, design-wise, why give up foreign keys? As mentioned in an ealier post, that is the WHOLE POINT...

  • RE: Starting and Stopping SQL Server Part 1

    <<In that case the only correct way of stopping the server is to use the cluster administrator tool. All methods mentioned in the article would create problems (server would try...

  • RE: sql backup to usb disk drive

    I would agree. I have never had good luck using network or USB devices to directly backup SQL Server databases. When using network storage, the backups would appear to complete....

  • RE: Restoring Database of 99GB ... if this take so long?

    To approximate backup/restore times, you really would have to run benchmarks on your own configuration. Even then, there are a lot of other facters that need to be taken into...

  • RE: Transaction log backup - A silly question

    Exactly. The typical sequence is backup the transaction log immediately before doing a full backup. This transaction log backup will rarely be needed in a restore situation because of its...

  • RE: Worst Practices - Making Databases Case Sensitive (Or Anything Else)

    I wouold agree with Andy's comment that making columns case-sensitive may be the best of both worlds.

    I guess that my real issue is that making the choice to implement a...

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