| Groups | Blog | Home |
sql server clients : Restoring a Single Table
I'm working for an online university, and we are currently in the process of redesigning our portal website. We were thinking of using a single database to store content, quizzes, and assignments coming from multiple courses, as well as user accounts and security. The reason for this, is that it simplifies generating reports for students taking multiple courses (eg.:, student transcript), teachers requesting reports (gradebook), etc. During the design process, we asked how can sql server 2005 maintain high availability? Also, what if only a single table got accidently deleted, or currupted. How can we restore that table without affecting other tables, and in the process keep the database online while restoring? So here's my question, is there a way to restore a single table without affecting other tables in the same database. Secondly, is there a way of maintaining high availability with a single huge database with lots of users commiting changes (eg, students writing quizzes, teachers adding content, admin staff moderating forums)? Thanks in advance Francis
1. Yes, you can restore single table without affecting other tables while
keeping the rest of database online if - other tables are not depend on this table - this table (or just partition to be restored) lives in a separate filegroup - you're using Enterprise Edition ;-) Of course, you can always do the same on any edition (regardless of physically data placement) by (entirely) replace data in (recreated) table with data from a database snapshot or from recent backup (which you may restore under another name on the same or another instance of SQL Server) 2. There are many HA features in SQL Server 2005: failover clustering, log shipping, database mirroring (not supported in current release but maybe will after sp1)..., but none of them can be supported using single database, of course... %-\ -- WBR, Evergray -- Words mean nothing... [quoted text, click to view] "Francis Reed" <francis@econcordia.ca> wrote in message news:uzDD6psQGHA.4452@TK2MSFTNGP12.phx.gbl... > Hi > > I'm working for an online university, and we are currently in the process > of redesigning our portal website. We were thinking of using a single > database to store content, quizzes, and assignments coming from multiple > courses, as well as user accounts and security. The reason for this, is > that it simplifies generating reports for students taking multiple courses > (eg.:, student transcript), teachers requesting reports (gradebook), etc. > During the design process, we asked how can sql server 2005 maintain high > availability? Also, what if only a single table got accidently deleted, or > currupted. How can we restore that table without affecting other tables, > and in the process keep the database online while restoring? So here's my > question, is there a way to restore a single table without affecting other > tables in the same database. > > Secondly, is there a way of maintaining high availability with a single > huge database with lots of users commiting changes (eg, students writing > quizzes, teachers adding content, admin staff moderating forums)? > > Thanks in advance > Francis >
Hi
Thank you for the advice. I've tried looking at how to restore a filegroup using SQL Server Management Studio 2005, and I can't get it to work. To simulate an example of a currupted table, I simply delete a table from my database. Next, I try to restore the table using a previous filegroup backup, but it doesn't seem to work. Would you know of any tutorials, or examples that explain step by step on how to use SQL Server Management Studio 2005 to restore a filegroup? Thank you in advance Francis [quoted text, click to view] "Evergray" <forlists@mail.ru> wrote in message news:uZttAO2QGHA.5728@tk2msftngp13.phx.gbl... > 1. Yes, you can restore single table without affecting other tables while > keeping the rest of database online if > - other tables are not depend on this table > - this table (or just partition to be restored) lives in a separate > filegroup > - you're using Enterprise Edition ;-) > > Of course, you can always do the same on any edition (regardless of > physically data placement) by (entirely) replace data in (recreated) table > with data from a database snapshot or from recent backup (which you may > restore under another name on the same or another instance of SQL Server) > > 2. There are many HA features in SQL Server 2005: failover clustering, log > shipping, database mirroring (not supported in current release but maybe > will after sp1)..., but none of them can be supported using single > database, of course... %-\ > > -- > WBR, Evergray > -- > Words mean nothing... > > > "Francis Reed" <francis@econcordia.ca> wrote in message > news:uzDD6psQGHA.4452@TK2MSFTNGP12.phx.gbl... >> Hi >> >> I'm working for an online university, and we are currently in the process >> of redesigning our portal website. We were thinking of using a single >> database to store content, quizzes, and assignments coming from multiple >> courses, as well as user accounts and security. The reason for this, is >> that it simplifies generating reports for students taking multiple >> courses (eg.:, student transcript), teachers requesting reports >> (gradebook), etc. During the design process, we asked how can sql server >> 2005 maintain high availability? Also, what if only a single table got >> accidently deleted, or currupted. How can we restore that table without >> affecting other tables, and in the process keep the database online while >> restoring? So here's my question, is there a way to restore a single >> table without affecting other tables in the same database. >> >> Secondly, is there a way of maintaining high availability with a single >> huge database with lots of users commiting changes (eg, students writing >> quizzes, teachers adding content, admin staff moderating forums)? >> >> Thanks in advance >> Francis >> > >
There are How To topics in books online for backup and
restore. They include file and filegroup backup/restore. The online version is at: http://msdn2.microsoft.com/en-US/library/ms189621.aspx You could also look at restoring the backup of the database to another server or another location copying the table from the restored database to the production database. High availability involves a lot of considerations and you may want to read up more on some of the things to address depending on the business needs. One source would be the MS SQL Server High Availability - for 2000 but still covers a lot of issues and approaches that apply to 2005: http://www.microsoft.com/mspress/books/6515.asp SQL Server magazine has published a lot of articles on the topic, addressing different issue, recovery requirements: http://www.windowsitpro.com/SQLServer Other things such as database snapshots, mirroring are new features in 2005 that can be looked at depending on your needs. You can find information on some of the new features to support different availability requirements by searching on High Availability in books online. -Sue On Thu, 9 Mar 2006 11:41:58 -0500, "Francis Reed" [quoted text, click to view] <francis@econcordia.ca> wrote:
>Hi > >Thank you for the advice. I've tried looking at how to restore a filegroup >using SQL Server Management Studio 2005, and I can't get it to work. To >simulate an example of a currupted table, I simply delete a table from my >database. Next, I try to restore the table using a previous filegroup >backup, but it doesn't seem to work. Would you know of any tutorials, or >examples that explain step by step on how to use SQL Server Management >Studio 2005 to restore a filegroup? > >Thank you in advance >Francis > > >"Evergray" <forlists@mail.ru> wrote in message >news:uZttAO2QGHA.5728@tk2msftngp13.phx.gbl... >> 1. Yes, you can restore single table without affecting other tables while >> keeping the rest of database online if >> - other tables are not depend on this table >> - this table (or just partition to be restored) lives in a separate >> filegroup >> - you're using Enterprise Edition ;-) >> >> Of course, you can always do the same on any edition (regardless of >> physically data placement) by (entirely) replace data in (recreated) table >> with data from a database snapshot or from recent backup (which you may >> restore under another name on the same or another instance of SQL Server) >> >> 2. There are many HA features in SQL Server 2005: failover clustering, log >> shipping, database mirroring (not supported in current release but maybe >> will after sp1)..., but none of them can be supported using single >> database, of course... %-\ >> >> -- >> WBR, Evergray >> -- >> Words mean nothing... >> >> >> "Francis Reed" <francis@econcordia.ca> wrote in message >> news:uzDD6psQGHA.4452@TK2MSFTNGP12.phx.gbl... >>> Hi >>> >>> I'm working for an online university, and we are currently in the process >>> of redesigning our portal website. We were thinking of using a single >>> database to store content, quizzes, and assignments coming from multiple >>> courses, as well as user accounts and security. The reason for this, is >>> that it simplifies generating reports for students taking multiple >>> courses (eg.:, student transcript), teachers requesting reports >>> (gradebook), etc. During the design process, we asked how can sql server >>> 2005 maintain high availability? Also, what if only a single table got >>> accidently deleted, or currupted. How can we restore that table without >>> affecting other tables, and in the process keep the database online while >>> restoring? So here's my question, is there a way to restore a single >>> table without affecting other tables in the same database. >>> >>> Secondly, is there a way of maintaining high availability with a single >>> huge database with lots of users commiting changes (eg, students writing >>> quizzes, teachers adding content, admin staff moderating forums)? >>> >>> Thanks in advance >>> Francis >>> >> >> >
Don't see what you're looking for? Try a search.
|
March 2003
May 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |