Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>1 - How are you backing up the data? Maintenance plans? </p> <p>2 - If you are appending to the same database backup file, the backup will grow!</p> <p>Check out the contents of the file. </p> <pre><code>RESTORE FILELISTONLY FROM AdventureWorksBackups WITH FILE=1; </code></pre> <p><a href="http://technet.microsoft.com/en-us/library/ms173778.aspx" rel="nofollow">http://technet.microsoft.com/en-us/library/ms173778.aspx</a></p> <p>This assumes you have a dump device named AdventureWorksBackups. You can also change it to a DISK='AdventureWorks.bak'.</p> <p>3 - Also, the maintenance plans do not do a good job with determining when to re-organize/update stats versus rebuild an index.</p> <p>4 - Check out the ola hallengren scripts. They are way better! </p> <p><a href="http://ola.hallengren.com/" rel="nofollow">http://ola.hallengren.com/</a></p> <p>First, they create a directory structure for you.</p> <pre><code>c:\backup\&lt;server name&gt;\&lt;database name&gt;\full c:\backup\&lt;server name&gt;\&lt;database name&gt;\diff c:\backup\&lt;server name&gt;\&lt;database name&gt;\log </code></pre> <p>Second, each backup has a date time stamp. No appending to backup files.</p> <p>Third, they clean up after themselves by passing the number of hours to keep on-line.</p> <p>Fourth, they handle index fragmentation better - 5-30 = re-organize or 30+ = rebuild.</p> <p>I usually set up the following for my databases.</p> <p>1 - system databases - full backup every night, log backups hourly.</p> <p>2 - user databases - full backup 1 x week, diff backup x 6 days, log backups hourly</p> <p>Last but not least, SQL Server 2005 does not have native support for compressed backups. This does not mean you can not run a batch file to zip them up afterwards.</p> <p>Third party tools like QUEST (DELL) and RED GATE used to support their own backup utility. The main reason was to fill this gap. Since SQL Server 2008, compressed backups were available. I think many of the vendors are getting rid of this utility since it is now standard.</p>
    singulars
    1. This table or related slice is empty.
    1. PODatabase backup size conundrum
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USCRAFTY DBA
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COEvery backup go to a different file (date time stamp). And I use the IndexOptimize script from .hallengren weekly.
      singulars
      1. PO
      1. USAllen King
    2. COWhat are you using? Maintenance plans? What is the recovery model?
      singulars
      1. PO
      1. USCRAFTY DBA
    3. COFor backup, yes, maintenance plan. Full backup runs every night. ola.hallengren.com script to optimize indexes runs every week.
      singulars
      1. PO
      1. USAllen King
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload