Showing posts with label important. Show all posts
Showing posts with label important. Show all posts

Thursday, March 22, 2012

DB Structure

As my learning process continues, I have found that Database structure is probably the most important & most difficutl part of development. Like database normallization etc.

How can I master database structure, ? but I want learning other than any database software like Access or SQL Server, I m looking for a generallized learning.

Will some1 give me assistance ...

If you are developing a Database application, yes it is important. But this is not really the group where this question is asked and I will move the post on to the SQL Server groups as this is probably the better group..

But for general database design I would suggest getting yourself a good book on Database design, One of the books that I keep on my desk is "Pro SQL Server 2005 Database Design and Optimization" by Louis Davidson (Apress) ISBN:1-59059-529-7. This book is based on SQL Server 2005 but the first half of the book deals with the basic design principles.

|||

Another 'must have', and also not product specific:

Handbook of Relational Database Design
by Candace C. Fleming, Barbara von Halle
ISBN: 0201114348

/Kenneth

sql

Friday, February 24, 2012

DB Maintenance Plan

I have a SQL 2000 server that has a small but very important database (about 5GB). The current maintenance plan does trans logs every hour and full every day. Currently they are to file on the same drive array. I would like to send them to a share on another server just to be really safe.

Would it be better to

1. Redirect the maintenance plan so that trans logs and backups go directly to the share

or

2. Keep the maintenance plan back ups to the current location and write a script that runs every hour and copies the .bak files to the share.

Also, since the database is so small should I just do full backups every hour instead of transaction?

Hi,

assuming your DB recovery model is full , perform T-Log backup on hourly interval and daily differential backup and weekly full backup....

but ultimately its upto your requirement performing T-Log backup regularly will helps you recover point in time.

Regards

Hemantgiri S. Goswami

|||

Thanks for the tip regarding backup types.

What about getting the backups off of the SQL server? Should I redirect them during the backup process or should I let them go to a local drive and them copy them elsewhere?

|||

Hi,

Copy them on Network after taking backup on local drive. The reason is suppose their is a network congession or slow network connection while you taking backup dirctly on Network Drive you may get poor response and might be fails to write backup.

Refer below links for more

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=936771&SiteID=1

http://searchsqlserver.techtarget.com/featuredTopic/0,290042,sid87_gci1144141,00.html

http://www.lazydba.com/sql/1__849.html

http://www.windowsitpro.com/Article/ArticleID/14025/14025.html

http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=6096

HTH

Hemantgiri S. Goswami

DB Maintenance Plan

I have a SQL 2000 server that has a small but very important database (about 5GB). The current maintenance plan does trans logs every hour and full every day. Currently they are to file on the same drive array. I would like to send them to a share on another server just to be really safe.

Would it be better to

1. Redirect the maintenance plan so that trans logs and backups go directly to the share

or

2. Keep the maintenance plan back ups to the current location and write a script that runs every hour and copies the .bak files to the share.

Also, since the database is so small should I just do full backups every hour instead of transaction?

Hi,

assuming your DB recovery model is full , perform T-Log backup on hourly interval and daily differential backup and weekly full backup....

but ultimately its upto your requirement performing T-Log backup regularly will helps you recover point in time.

Regards

Hemantgiri S. Goswami

|||

Thanks for the tip regarding backup types.

What about getting the backups off of the SQL server? Should I redirect them during the backup process or should I let them go to a local drive and them copy them elsewhere?

|||

Hi,

Copy them on Network after taking backup on local drive. The reason is suppose their is a network congession or slow network connection while you taking backup dirctly on Network Drive you may get poor response and might be fails to write backup.

Refer below links for more

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=936771&SiteID=1

http://searchsqlserver.techtarget.com/featuredTopic/0,290042,sid87_gci1144141,00.html

http://www.lazydba.com/sql/1__849.html

http://www.windowsitpro.com/Article/ArticleID/14025/14025.html

http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=6096

HTH

Hemantgiri S. Goswami