| Author |
 Topic  |
|
|
Astralis
Senior Member
USA
1218 Posts |
 Posted - 27 May 2008 : 00:59:31
|
I've just now upgraded from 2000 to 2005 Express. I simply "restored" the 2000 .bak file of the database and it works. Is there anything that's recommended that I should do with SQL Server 2005 Express to the database to make sure it runs smooth beyond installing the .bak file?
Also, for backing up the db, what are some of the best practices people use? If you backup, how often, and how do you do it?< |
Edited by - Astralis on 27 May 2008 01:26:47 |
|
|
HuwR
Forum Admin
United Kingdom
20584 Posts |
Posted - 27 May 2008 : 01:55:08
|
| make sure it backed up the indexes.< |
 |
|
|
Astralis
Senior Member
USA
1218 Posts |
Posted - 27 May 2008 : 02:31:48
|
I see them and it appears they're working correctly.
Another concern: using MS 2008, when I open up the Reliability and Performance Tab, under "network", I see sqlserver.exe with the ADDRESS as "mail" and it's sending lots of data. Can anyone confirm what this means? Is this normal and simply the SQLServer running despite the weird address name?< |
|
|
|
Podge
Support Moderator
Ireland
3775 Posts |
|
|
Astralis
Senior Member
USA
1218 Posts |
Posted - 28 May 2008 : 04:47:23
|
Windows Server 2008.
A few questions about backing up so much data:
1. If I use SQLSafe, can I keep a single back-up and discard the old ones? How many back-ups should I keep before discarding them? One week? Is there a best practice about this?
2. If I'm constantly writing and deleting data, will this decrease the performance of the disk as the needle (?) has to move all over the platter to find data written in different sections? What's the best way to avoid this?
3. If I'm forced to defragment the drive because of the large deletions (and therefore large, empty spaces), doesn't that require the entire server to be shut down as it defragments the disk?< |
|
|
|
HuwR
Forum Admin
United Kingdom
20584 Posts |
Posted - 28 May 2008 : 06:37:43
|
quote:
If I'm constantly writing and deleting data, will this decrease the performance of the disk as the needle (?) has to move all over the platter to find data written in different sections? What's the best way to avoid this?
for sql it will not have much impact unless you are actually constantly increasing db sizes etc, when you setup a database you should create it with a reasonably large initial size, SQL will then imediately allocate this space for the db, the underlying OS filesystem is not used by SQL, it uses its own filing system< |
|
|
|
Podge
Support Moderator
Ireland
3775 Posts |
|
| |
Topic |
|
Topic Locked
