I just restored a database (.bak file) using SQL Server 2005. The database
now shows up but has "(6.5 Compatible)" next to it and no "+" next to it to
expand the tree, see tables, etc.
Any idea how I make this database accessible? I can do what I want with
it.. if I need to run an upgrade wizard or something, please let me know.
Thanks,
RonCheck out sp_dbcmptlevel in the BOL.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"Ronald S. Cook" <rcook@.westinis.com> wrote in message
news:OHYUBqKPGHA.2888@.tk2msftngp13.phx.gbl...
I just restored a database (.bak file) using SQL Server 2005. The database
now shows up but has "(6.5 Compatible)" next to it and no "+" next to it to
expand the tree, see tables, etc.
Any idea how I make this database accessible? I can do what I want with
it.. if I need to run an upgrade wizard or something, please let me know.
Thanks,
Ron|||Ronald S. Cook (rcook@.westinis.com) writes:
> I just restored a database (.bak file) using SQL Server 2005. The
> database now shows up but has "(6.5 Compatible)" next to it and no "+"
> next to it to expand the tree, see tables, etc.
> Any idea how I make this database accessible? I can do what I want with
> it.. if I need to run an upgrade wizard or something, please let me know.
All it means is that the database is in compatibility-level mode 65. You
can still access it from the Query Editor and run queries against it. But
apparently you cannot connect to it from Object Browser.
To be able to do that, you can run:
EXEC sp_dbcmptlevel yourdb, 90
90 where means SQL 2005. You can also use 80 for SQL 2000 or 70 for
SQL 7. The one catch there is with chaning the compatinility level, is
that there may be stored procedures or triggers in the database that
relies on SQL 6.5 behaviour.
HAd the database actually been a 6.5 database, you would have been able to
restore the database at all.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx
Showing posts with label bak. Show all posts
Showing posts with label bak. Show all posts
Wednesday, March 7, 2012
Sunday, February 19, 2012
Hot Backup
Someone told me should backup the live data files (files with
extension MDF and LDF) instead of the backup files (file with
extension BAK) in hot backup. I don't think it work in the case I need
to restore these data files from tape backup. Am I correct?That person might be thinking about the various type of snapshot backup products that exists. This
type of backup uses some technique to "freeze" the I/O for some period of time and then use some
journaling to keep track of the modifications performed while the backup is running (while you are
copying the files). There's some information in SQL Server 2005 Books Online, search for instance
for "VSS Writer" (which is the service in SQL server to assist these types of backup programs).
But in general you are right. You don't want to just "grab the database files".
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<viet@.rocketmail.com> wrote in message
news:2341c184-ec8b-42d7-b250-3e5acd594e49@.w8g2000prd.googlegroups.com...
> Someone told me should backup the live data files (files with
> extension MDF and LDF) instead of the backup files (file with
> extension BAK) in hot backup. I don't think it work in the case I need
> to restore these data files from tape backup. Am I correct?|||On Apr 24, 6:47=A0pm, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> That person might be thinking about the various type of snapshot backup pr=oducts that exists. This
> type of backup uses some technique to "freeze" the I/O for some period of =time and then use some
> journaling to keep track of the modifications performed while the backup i=s running (while you are
> copying the files). There's some information in SQL Server 2005 Books Onli=ne, search for instance
> for "VSS Writer" (which is the service in SQL server to assist these types= of backup programs).
> But in general you are right. You don't want to just "grab the database fi=les".
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asph=
ttp://sqlblog.com/blogs/tibor_karaszi
> <v...@.rocketmail.com> wrote in message
> news:2341c184-ec8b-42d7-b250-3e5acd594e49@.w8g2000prd.googlegroups.com...
>
> > Someone told me should backup the live data files (files with
> > extension MDF and LDF) instead of the backup files (file with
> > extension BAK) in hot backup. I don't think it work in the case I need
> > to restore these data files from tape backup. Am I correct... Hide quoted= text -
> - Show quoted text -
If the intention is to backup the database before tape backup . You
can always schedule the db backups online before tape backup and
the .bak files can be backed up on tape.
If the database size is very large you can use the tools like
Litespeed which will help you to save on time.
Thanks
Ajay Rengunthwar
MCTS,MCDBA,MCAD
extension MDF and LDF) instead of the backup files (file with
extension BAK) in hot backup. I don't think it work in the case I need
to restore these data files from tape backup. Am I correct?That person might be thinking about the various type of snapshot backup products that exists. This
type of backup uses some technique to "freeze" the I/O for some period of time and then use some
journaling to keep track of the modifications performed while the backup is running (while you are
copying the files). There's some information in SQL Server 2005 Books Online, search for instance
for "VSS Writer" (which is the service in SQL server to assist these types of backup programs).
But in general you are right. You don't want to just "grab the database files".
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<viet@.rocketmail.com> wrote in message
news:2341c184-ec8b-42d7-b250-3e5acd594e49@.w8g2000prd.googlegroups.com...
> Someone told me should backup the live data files (files with
> extension MDF and LDF) instead of the backup files (file with
> extension BAK) in hot backup. I don't think it work in the case I need
> to restore these data files from tape backup. Am I correct?|||On Apr 24, 6:47=A0pm, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> That person might be thinking about the various type of snapshot backup pr=oducts that exists. This
> type of backup uses some technique to "freeze" the I/O for some period of =time and then use some
> journaling to keep track of the modifications performed while the backup i=s running (while you are
> copying the files). There's some information in SQL Server 2005 Books Onli=ne, search for instance
> for "VSS Writer" (which is the service in SQL server to assist these types= of backup programs).
> But in general you are right. You don't want to just "grab the database fi=les".
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asph=
ttp://sqlblog.com/blogs/tibor_karaszi
> <v...@.rocketmail.com> wrote in message
> news:2341c184-ec8b-42d7-b250-3e5acd594e49@.w8g2000prd.googlegroups.com...
>
> > Someone told me should backup the live data files (files with
> > extension MDF and LDF) instead of the backup files (file with
> > extension BAK) in hot backup. I don't think it work in the case I need
> > to restore these data files from tape backup. Am I correct... Hide quoted= text -
> - Show quoted text -
If the intention is to backup the database before tape backup . You
can always schedule the db backups online before tape backup and
the .bak files can be backed up on tape.
If the database size is very large you can use the tools like
Litespeed which will help you to save on time.
Thanks
Ajay Rengunthwar
MCTS,MCDBA,MCAD
Subscribe to:
Posts (Atom)