Just to be clear, I am not restoring to a different machine. Just trying to
create a new database (which is not hanging from my first attempt) from an
existing database.
TahnksActually, it seems that RECOVERY is the default, so maybe I don't need to
specify it.
A better command might be
RESTORE DATABASE stuckdb
FROM c:\mybackups\template.bak
WITH REPLACE|||Well, that did not work. It says no entry in sysdevices for
'c:\mybackups\template.bak'|||Tried adding DISK and putting a single quote around the path. Seems to have
worked.
Thanks!
> RESTORE DATABASE stuckdb
> FROM DISK = 'c:\mybackups\template.bak'
> WITH REPLACE|||"mike" <mike@.commmcasssttt.com> wrote in message
news:12a7td2rqcpoo7d@.corp.supernews.com...
> Well, that did not work. It says no entry in sysdevices for
> 'c:\mybackups\template.bak'
>
below is a script that you can adapt for your own purposes. You really need
to read BOL for the commands involved to make sure you understand exactly
what happens. BOL also has many useful examples. To restore to a new
database from a backup of an existing database (the template in your
description), just use a new database name in the restore command ("test_db"
in this example) and be sure to specify the files you want to use for the
database (the move options). The 2nd command is useful to identify the
logical names (used by the database in the backup) that need to be moved.
use master
go
exec xp_cmdshell 'dir C:\sql2k\MSSQL\BACKUP\ /o-d'
go
RESTORE FILELISTONLY
FROM DISK='C:\sql2k\MSSQL\BACKUP\save_me.BAK'
GO
RESTORE DATABASE test_db
FROM DISK='C:\sql2k\MSSQL\BACKUP\save_me.BAK'
WITH RECOVERY, STATS, REPLACE,
MOVE 'main_Data' TO 'C:\sql2k\MSSQL\DATA\test_db_DATA.mdf',
MOVE 'main_Log' TO 'C:\sql2k\MSSQL\DATA\test_db_Log.ldf'
GO|||Thanks to those who responded earlier. If someone would check my commands
below, I would appreciate it.
Again, what I tried to do is create a new database from an existing template
database. To do this, I tried (in Enterprise Manager) to restore from the
template to a new database name. However, something went wrong and at the
end of the restore process I got an error about "log begins at 30000 and is
too late to apply to database." The new database is stuck with a (loading)
next to it.
So I am going to try to do it in Query AnalyzeR with the RECOVERY option.
After trying to decipher the books online, this is what I came up with:
RESTORE DATABASE stuckdb
FROM c:\mybackups\template.bak
WITH RECOVERY, REPLACE
Thank you|||Just to be clear, I am not restoring to a different machine. Just trying to
create a new database (which is not hanging from my first attempt) from an
existing database.
Tahnks|||Actually, it seems that RECOVERY is the default, so maybe I don't need to
specify it.
A better command might be
RESTORE DATABASE stuckdb
FROM c:\mybackups\template.bak
WITH REPLACE|||Well, that did not work. It says no entry in sysdevices for
'c:\mybackups\template.bak'|||Tried adding DISK and putting a single quote around the path. Seems to have
worked.
Thanks!
> RESTORE DATABASE stuckdb
> FROM DISK = 'c:\mybackups\template.bak'
> WITH REPLACE
Showing posts with label machine. Show all posts
Showing posts with label machine. Show all posts
Wednesday, March 28, 2012
Monday, March 26, 2012
Restore to different file size
My production database files total about 100GB, of which about 35GB is used.
My test machine has about 60GB available, so has plenty of room to
accommodate the entire database. When I try to restore a full backup though,
it screams at me that there is not enough disk space.
I created a new database with 40GB of data files, and that should be enough
to hold all the data. How can I keep the restore process from trying to
create exactly the same file configuration as the original database?
You can't.
The SQL restore process requires the creation of exactly the same file sizes
on the target system as existed on the originating system. I suggest
purchasing an external HDD, restorign to that, shrinking, then moving the
data files.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Daniel Rimmelzwaan (MVP - Dynamics NAV)" <daniel@.nadaspam.risplus.com>
wrote in message news:Ow$oUoH0HHA.1168@.TK2MSFTNGP02.phx.gbl...
> My production database files total about 100GB, of which about 35GB is
> used. My test machine has about 60GB available, so has plenty of room to
> accommodate the entire database. When I try to restore a full backup
> though, it screams at me that there is not enough disk space.
> I created a new database with 40GB of data files, and that should be
> enough to hold all the data. How can I keep the restore process from
> trying to create exactly the same file configuration as the original
> database?
|||I was afraid of that. Thanks Geoff.
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OcDFQuH0HHA.1208@.TK2MSFTNGP03.phx.gbl...
> You can't.
> The SQL restore process requires the creation of exactly the same file
> sizes on the target system as existed on the originating system. I
> suggest purchasing an external HDD, restorign to that, shrinking, then
> moving the data files.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
>
> "Daniel Rimmelzwaan (MVP - Dynamics NAV)" <daniel@.nadaspam.risplus.com>
> wrote in message news:Ow$oUoH0HHA.1168@.TK2MSFTNGP02.phx.gbl...
>
My test machine has about 60GB available, so has plenty of room to
accommodate the entire database. When I try to restore a full backup though,
it screams at me that there is not enough disk space.
I created a new database with 40GB of data files, and that should be enough
to hold all the data. How can I keep the restore process from trying to
create exactly the same file configuration as the original database?
You can't.
The SQL restore process requires the creation of exactly the same file sizes
on the target system as existed on the originating system. I suggest
purchasing an external HDD, restorign to that, shrinking, then moving the
data files.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Daniel Rimmelzwaan (MVP - Dynamics NAV)" <daniel@.nadaspam.risplus.com>
wrote in message news:Ow$oUoH0HHA.1168@.TK2MSFTNGP02.phx.gbl...
> My production database files total about 100GB, of which about 35GB is
> used. My test machine has about 60GB available, so has plenty of room to
> accommodate the entire database. When I try to restore a full backup
> though, it screams at me that there is not enough disk space.
> I created a new database with 40GB of data files, and that should be
> enough to hold all the data. How can I keep the restore process from
> trying to create exactly the same file configuration as the original
> database?
|||I was afraid of that. Thanks Geoff.
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OcDFQuH0HHA.1208@.TK2MSFTNGP03.phx.gbl...
> You can't.
> The SQL restore process requires the creation of exactly the same file
> sizes on the target system as existed on the originating system. I
> suggest purchasing an external HDD, restorign to that, shrinking, then
> moving the data files.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
>
> "Daniel Rimmelzwaan (MVP - Dynamics NAV)" <daniel@.nadaspam.risplus.com>
> wrote in message news:Ow$oUoH0HHA.1168@.TK2MSFTNGP02.phx.gbl...
>
Restore to different file size
My production database files total about 100GB, of which about 35GB is used.
My test machine has about 60GB available, so has plenty of room to
accommodate the entire database. When I try to restore a full backup though,
it screams at me that there is not enough disk space.
I created a new database with 40GB of data files, and that should be enough
to hold all the data. How can I keep the restore process from trying to
create exactly the same file configuration as the original database?You can't.
The SQL restore process requires the creation of exactly the same file sizes
on the target system as existed on the originating system. I suggest
purchasing an external HDD, restorign to that, shrinking, then moving the
data files.
--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Daniel Rimmelzwaan (MVP - Dynamics NAV)" <daniel@.nadaspam.risplus.com>
wrote in message news:Ow$oUoH0HHA.1168@.TK2MSFTNGP02.phx.gbl...
> My production database files total about 100GB, of which about 35GB is
> used. My test machine has about 60GB available, so has plenty of room to
> accommodate the entire database. When I try to restore a full backup
> though, it screams at me that there is not enough disk space.
> I created a new database with 40GB of data files, and that should be
> enough to hold all the data. How can I keep the restore process from
> trying to create exactly the same file configuration as the original
> database?|||I was afraid of that. Thanks Geoff.
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OcDFQuH0HHA.1208@.TK2MSFTNGP03.phx.gbl...
> You can't.
> The SQL restore process requires the creation of exactly the same file
> sizes on the target system as existed on the originating system. I
> suggest purchasing an external HDD, restorign to that, shrinking, then
> moving the data files.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
>
> "Daniel Rimmelzwaan (MVP - Dynamics NAV)" <daniel@.nadaspam.risplus.com>
> wrote in message news:Ow$oUoH0HHA.1168@.TK2MSFTNGP02.phx.gbl...
>> My production database files total about 100GB, of which about 35GB is
>> used. My test machine has about 60GB available, so has plenty of room to
>> accommodate the entire database. When I try to restore a full backup
>> though, it screams at me that there is not enough disk space.
>> I created a new database with 40GB of data files, and that should be
>> enough to hold all the data. How can I keep the restore process from
>> trying to create exactly the same file configuration as the original
>> database?
>
My test machine has about 60GB available, so has plenty of room to
accommodate the entire database. When I try to restore a full backup though,
it screams at me that there is not enough disk space.
I created a new database with 40GB of data files, and that should be enough
to hold all the data. How can I keep the restore process from trying to
create exactly the same file configuration as the original database?You can't.
The SQL restore process requires the creation of exactly the same file sizes
on the target system as existed on the originating system. I suggest
purchasing an external HDD, restorign to that, shrinking, then moving the
data files.
--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Daniel Rimmelzwaan (MVP - Dynamics NAV)" <daniel@.nadaspam.risplus.com>
wrote in message news:Ow$oUoH0HHA.1168@.TK2MSFTNGP02.phx.gbl...
> My production database files total about 100GB, of which about 35GB is
> used. My test machine has about 60GB available, so has plenty of room to
> accommodate the entire database. When I try to restore a full backup
> though, it screams at me that there is not enough disk space.
> I created a new database with 40GB of data files, and that should be
> enough to hold all the data. How can I keep the restore process from
> trying to create exactly the same file configuration as the original
> database?|||I was afraid of that. Thanks Geoff.
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OcDFQuH0HHA.1208@.TK2MSFTNGP03.phx.gbl...
> You can't.
> The SQL restore process requires the creation of exactly the same file
> sizes on the target system as existed on the originating system. I
> suggest purchasing an external HDD, restorign to that, shrinking, then
> moving the data files.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
>
> "Daniel Rimmelzwaan (MVP - Dynamics NAV)" <daniel@.nadaspam.risplus.com>
> wrote in message news:Ow$oUoH0HHA.1168@.TK2MSFTNGP02.phx.gbl...
>> My production database files total about 100GB, of which about 35GB is
>> used. My test machine has about 60GB available, so has plenty of room to
>> accommodate the entire database. When I try to restore a full backup
>> though, it screams at me that there is not enough disk space.
>> I created a new database with 40GB of data files, and that should be
>> enough to hold all the data. How can I keep the restore process from
>> trying to create exactly the same file configuration as the original
>> database?
>
Restore to different file size
My production database files total about 100GB, of which about 35GB is used.
My test machine has about 60GB available, so has plenty of room to
accommodate the entire database. When I try to restore a full backup though,
it screams at me that there is not enough disk space.
I created a new database with 40GB of data files, and that should be enough
to hold all the data. How can I keep the restore process from trying to
create exactly the same file configuration as the original database?You can't.
The SQL restore process requires the creation of exactly the same file sizes
on the target system as existed on the originating system. I suggest
purchasing an external HDD, restorign to that, shrinking, then moving the
data files.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Daniel Rimmelzwaan (MVP - Dynamics NAV)" <daniel@.nadaspam.risplus.com>
wrote in message news:Ow$oUoH0HHA.1168@.TK2MSFTNGP02.phx.gbl...
> My production database files total about 100GB, of which about 35GB is
> used. My test machine has about 60GB available, so has plenty of room to
> accommodate the entire database. When I try to restore a full backup
> though, it screams at me that there is not enough disk space.
> I created a new database with 40GB of data files, and that should be
> enough to hold all the data. How can I keep the restore process from
> trying to create exactly the same file configuration as the original
> database?|||I was afraid of that. Thanks Geoff.
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OcDFQuH0HHA.1208@.TK2MSFTNGP03.phx.gbl...
> You can't.
> The SQL restore process requires the creation of exactly the same file
> sizes on the target system as existed on the originating system. I
> suggest purchasing an external HDD, restorign to that, shrinking, then
> moving the data files.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
>
> "Daniel Rimmelzwaan (MVP - Dynamics NAV)" <daniel@.nadaspam.risplus.com>
> wrote in message news:Ow$oUoH0HHA.1168@.TK2MSFTNGP02.phx.gbl...
>
My test machine has about 60GB available, so has plenty of room to
accommodate the entire database. When I try to restore a full backup though,
it screams at me that there is not enough disk space.
I created a new database with 40GB of data files, and that should be enough
to hold all the data. How can I keep the restore process from trying to
create exactly the same file configuration as the original database?You can't.
The SQL restore process requires the creation of exactly the same file sizes
on the target system as existed on the originating system. I suggest
purchasing an external HDD, restorign to that, shrinking, then moving the
data files.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Daniel Rimmelzwaan (MVP - Dynamics NAV)" <daniel@.nadaspam.risplus.com>
wrote in message news:Ow$oUoH0HHA.1168@.TK2MSFTNGP02.phx.gbl...
> My production database files total about 100GB, of which about 35GB is
> used. My test machine has about 60GB available, so has plenty of room to
> accommodate the entire database. When I try to restore a full backup
> though, it screams at me that there is not enough disk space.
> I created a new database with 40GB of data files, and that should be
> enough to hold all the data. How can I keep the restore process from
> trying to create exactly the same file configuration as the original
> database?|||I was afraid of that. Thanks Geoff.
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OcDFQuH0HHA.1208@.TK2MSFTNGP03.phx.gbl...
> You can't.
> The SQL restore process requires the creation of exactly the same file
> sizes on the target system as existed on the originating system. I
> suggest purchasing an external HDD, restorign to that, shrinking, then
> moving the data files.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
>
> "Daniel Rimmelzwaan (MVP - Dynamics NAV)" <daniel@.nadaspam.risplus.com>
> wrote in message news:Ow$oUoH0HHA.1168@.TK2MSFTNGP02.phx.gbl...
>
Friday, March 23, 2012
Restore SQL2K on different machine
Hello,
Would anyone know or recommend/advise the easiest approach in bringing down
and retiring an existing SQL2K running on W2K Server and brining it up with
all of the data, jobs, etc. onto a newer server machine? Wondering if there
was a way maybe do a full server restore from one of our server backup tapes
instead of having to reinstall/reconfigure everything from scratch.
Thanks in advance.Imaging is one approach if you have an imaging software like StorageCraft or
Acronis. But a main consideration here is hardware and configuration. The
source and destination may have different disk configurations. Another
considertation maybe to use Win2K3 instead of Win2K. If what you're
intending to restore is simply SQL Server, just a backup of all system and
user database would be enough and a very good restore process
On the old SQL Server instance,
1) stop all applications accessing your SQL Server
2) backup all your system and user databases
3) identify the latest hotfix you have. This is necessary for you to
restore on the new one
On the new SQL Server instance,
1) Install SQL Server together with the service packs and hotfixes up to the
one you have on the old instance
2) start SQL Server in single-user mode using the sqlservr.exe -c -m
3) restore the master database and restart the SQL Server service
4) restore the msdb database - be sure the SQLAgent service is not runnig
before you do so
5) restore model database if necessary
6) reconfigure your tempdb if necessary
7) restore all user databases and reconfigure if necessary - file locations
in particular
"zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
> Hello,
> Would anyone know or recommend/advise the easiest approach in bringing
> down and retiring an existing SQL2K running on W2K Server and brining it
> up with all of the data, jobs, etc. onto a newer server machine?
> Wondering if there was a way maybe do a full server restore from one of
> our server backup tapes instead of having to reinstall/reconfigure
> everything from scratch.
> Thanks in advance.
>|||Actually I personally am leaning more towards putting it on a w2k3 OS
instead of w2k but am concerned if there would be anything in w2k3 that
wouldn't support w2k as in the system files, ad/domain, etc? Like would you
happen to know if there were anything that was left out in w2k3 that was in
w2k?
Thanks a bunch for your quick and helpful reply. Much appreciated
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
> Imaging is one approach if you have an imaging software like StorageCraft
> or Acronis. But a main consideration here is hardware and configuration.
> The source and destination may have different disk configurations. Another
> considertation maybe to use Win2K3 instead of Win2K. If what you're
> intending to restore is simply SQL Server, just a backup of all system and
> user database would be enough and a very good restore process
> On the old SQL Server instance,
> 1) stop all applications accessing your SQL Server
> 2) backup all your system and user databases
> 3) identify the latest hotfix you have. This is necessary for you to
> restore on the new one
> On the new SQL Server instance,
> 1) Install SQL Server together with the service packs and hotfixes up to
> the one you have on the old instance
> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
> 3) restore the master database and restart the SQL Server service
> 4) restore the msdb database - be sure the SQLAgent service is not runnig
> before you do so
> 5) restore model database if necessary
> 6) reconfigure your tempdb if necessary
> 7) restore all user databases and reconfigure if necessary - file
> locations in particular
>
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>|||Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just remember
to ignore the warning when you install SQL Server 2000 on a Win2K3 telling
you that you do not have SP3. Install the latest service pack after
installing SQL Server 2000
"zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
> Actually I personally am leaning more towards putting it on a w2k3 OS
> instead of w2k but am concerned if there would be anything in w2k3 that
> wouldn't support w2k as in the system files, ad/domain, etc? Like would
> you happen to know if there were anything that was left out in w2k3 that
> was in w2k?
> Thanks a bunch for your quick and helpful reply. Much appreciated
>
> "bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
> news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
>|||I guess 2 main things that come to mind on that w2k server is that I've
installed a certificate from an ms ca service (in use for network ssl 'Force
protocol encryption' SQL Server Network Utility) in which I can just do
another certificate request/install and some .dll's that a VB app uses but I
would think that these shouldn't be an issue in that w2k3 would definitely
continue to support these. Will look into it further. Thanks so much for
your speedy informative reply. Will greatly help out in clearing things up
and expediting my research
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u$QuvTm3HHA.5724@.TK2MSFTNGP05.phx.gbl...
> Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just
> remember to ignore the warning when you install SQL Server 2000 on a
> Win2K3 telling you that you do not have SP3. Install the latest service
> pack after installing SQL Server 2000
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
>|||Sorry if I'm over analyzing this perhaps but I can't seem to visualize some
of the "X" factors like how to keep the same server name, domain and IP
address the same after rebuilding/restoring the master db onto the new
machine since this holds the domain logins/jobs. Are there any websites
that can layout it out step by step in retiring an old w2k-sql2k and restore
it onto a newer machine with w2k3-sql2k?
Thanks for your helpful replies bass_player.
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u$QuvTm3HHA.5724@.TK2MSFTNGP05.phx.gbl...
> Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just
> remember to ignore the warning when you install SQL Server 2000 on a
> Win2K3 telling you that you do not have SP3. Install the latest service
> pack after installing SQL Server 2000
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
>
Would anyone know or recommend/advise the easiest approach in bringing down
and retiring an existing SQL2K running on W2K Server and brining it up with
all of the data, jobs, etc. onto a newer server machine? Wondering if there
was a way maybe do a full server restore from one of our server backup tapes
instead of having to reinstall/reconfigure everything from scratch.
Thanks in advance.Imaging is one approach if you have an imaging software like StorageCraft or
Acronis. But a main consideration here is hardware and configuration. The
source and destination may have different disk configurations. Another
considertation maybe to use Win2K3 instead of Win2K. If what you're
intending to restore is simply SQL Server, just a backup of all system and
user database would be enough and a very good restore process
On the old SQL Server instance,
1) stop all applications accessing your SQL Server
2) backup all your system and user databases
3) identify the latest hotfix you have. This is necessary for you to
restore on the new one
On the new SQL Server instance,
1) Install SQL Server together with the service packs and hotfixes up to the
one you have on the old instance
2) start SQL Server in single-user mode using the sqlservr.exe -c -m
3) restore the master database and restart the SQL Server service
4) restore the msdb database - be sure the SQLAgent service is not runnig
before you do so
5) restore model database if necessary
6) reconfigure your tempdb if necessary
7) restore all user databases and reconfigure if necessary - file locations
in particular
"zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
> Hello,
> Would anyone know or recommend/advise the easiest approach in bringing
> down and retiring an existing SQL2K running on W2K Server and brining it
> up with all of the data, jobs, etc. onto a newer server machine?
> Wondering if there was a way maybe do a full server restore from one of
> our server backup tapes instead of having to reinstall/reconfigure
> everything from scratch.
> Thanks in advance.
>|||Actually I personally am leaning more towards putting it on a w2k3 OS
instead of w2k but am concerned if there would be anything in w2k3 that
wouldn't support w2k as in the system files, ad/domain, etc? Like would you
happen to know if there were anything that was left out in w2k3 that was in
w2k?
Thanks a bunch for your quick and helpful reply. Much appreciated
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
> Imaging is one approach if you have an imaging software like StorageCraft
> or Acronis. But a main consideration here is hardware and configuration.
> The source and destination may have different disk configurations. Another
> considertation maybe to use Win2K3 instead of Win2K. If what you're
> intending to restore is simply SQL Server, just a backup of all system and
> user database would be enough and a very good restore process
> On the old SQL Server instance,
> 1) stop all applications accessing your SQL Server
> 2) backup all your system and user databases
> 3) identify the latest hotfix you have. This is necessary for you to
> restore on the new one
> On the new SQL Server instance,
> 1) Install SQL Server together with the service packs and hotfixes up to
> the one you have on the old instance
> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
> 3) restore the master database and restart the SQL Server service
> 4) restore the msdb database - be sure the SQLAgent service is not runnig
> before you do so
> 5) restore model database if necessary
> 6) reconfigure your tempdb if necessary
> 7) restore all user databases and reconfigure if necessary - file
> locations in particular
>
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>|||Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just remember
to ignore the warning when you install SQL Server 2000 on a Win2K3 telling
you that you do not have SP3. Install the latest service pack after
installing SQL Server 2000
"zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
> Actually I personally am leaning more towards putting it on a w2k3 OS
> instead of w2k but am concerned if there would be anything in w2k3 that
> wouldn't support w2k as in the system files, ad/domain, etc? Like would
> you happen to know if there were anything that was left out in w2k3 that
> was in w2k?
> Thanks a bunch for your quick and helpful reply. Much appreciated
>
> "bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
> news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
>|||I guess 2 main things that come to mind on that w2k server is that I've
installed a certificate from an ms ca service (in use for network ssl 'Force
protocol encryption' SQL Server Network Utility) in which I can just do
another certificate request/install and some .dll's that a VB app uses but I
would think that these shouldn't be an issue in that w2k3 would definitely
continue to support these. Will look into it further. Thanks so much for
your speedy informative reply. Will greatly help out in clearing things up
and expediting my research
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u$QuvTm3HHA.5724@.TK2MSFTNGP05.phx.gbl...
> Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just
> remember to ignore the warning when you install SQL Server 2000 on a
> Win2K3 telling you that you do not have SP3. Install the latest service
> pack after installing SQL Server 2000
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
>|||Sorry if I'm over analyzing this perhaps but I can't seem to visualize some
of the "X" factors like how to keep the same server name, domain and IP
address the same after rebuilding/restoring the master db onto the new
machine since this holds the domain logins/jobs. Are there any websites
that can layout it out step by step in retiring an old w2k-sql2k and restore
it onto a newer machine with w2k3-sql2k?
Thanks for your helpful replies bass_player.
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u$QuvTm3HHA.5724@.TK2MSFTNGP05.phx.gbl...
> Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just
> remember to ignore the warning when you install SQL Server 2000 on a
> Win2K3 telling you that you do not have SP3. Install the latest service
> pack after installing SQL Server 2000
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
>
Restore SQL2K on different machine
Hello,
Would anyone know or recommend/advise the easiest approach in bringing down
and retiring an existing SQL2K running on W2K Server and brining it up with
all of the data, jobs, etc. onto a newer server machine? Wondering if there
was a way maybe do a full server restore from one of our server backup tapes
instead of having to reinstall/reconfigure everything from scratch.
Thanks in advance.
Imaging is one approach if you have an imaging software like StorageCraft or
Acronis. But a main consideration here is hardware and configuration. The
source and destination may have different disk configurations. Another
considertation maybe to use Win2K3 instead of Win2K. If what you're
intending to restore is simply SQL Server, just a backup of all system and
user database would be enough and a very good restore process
On the old SQL Server instance,
1) stop all applications accessing your SQL Server
2) backup all your system and user databases
3) identify the latest hotfix you have. This is necessary for you to
restore on the new one
On the new SQL Server instance,
1) Install SQL Server together with the service packs and hotfixes up to the
one you have on the old instance
2) start SQL Server in single-user mode using the sqlservr.exe -c -m
3) restore the master database and restart the SQL Server service
4) restore the msdb database - be sure the SQLAgent service is not runnig
before you do so
5) restore model database if necessary
6) reconfigure your tempdb if necessary
7) restore all user databases and reconfigure if necessary - file locations
in particular
"zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
> Hello,
> Would anyone know or recommend/advise the easiest approach in bringing
> down and retiring an existing SQL2K running on W2K Server and brining it
> up with all of the data, jobs, etc. onto a newer server machine?
> Wondering if there was a way maybe do a full server restore from one of
> our server backup tapes instead of having to reinstall/reconfigure
> everything from scratch.
> Thanks in advance.
>
|||Actually I personally am leaning more towards putting it on a w2k3 OS
instead of w2k but am concerned if there would be anything in w2k3 that
wouldn't support w2k as in the system files, ad/domain, etc? Like would you
happen to know if there were anything that was left out in w2k3 that was in
w2k?
Thanks a bunch for your quick and helpful reply. Much appreciated
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
> Imaging is one approach if you have an imaging software like StorageCraft
> or Acronis. But a main consideration here is hardware and configuration.
> The source and destination may have different disk configurations. Another
> considertation maybe to use Win2K3 instead of Win2K. If what you're
> intending to restore is simply SQL Server, just a backup of all system and
> user database would be enough and a very good restore process
> On the old SQL Server instance,
> 1) stop all applications accessing your SQL Server
> 2) backup all your system and user databases
> 3) identify the latest hotfix you have. This is necessary for you to
> restore on the new one
> On the new SQL Server instance,
> 1) Install SQL Server together with the service packs and hotfixes up to
> the one you have on the old instance
> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
> 3) restore the master database and restart the SQL Server service
> 4) restore the msdb database - be sure the SQLAgent service is not runnig
> before you do so
> 5) restore model database if necessary
> 6) reconfigure your tempdb if necessary
> 7) restore all user databases and reconfigure if necessary - file
> locations in particular
>
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>
|||Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just remember
to ignore the warning when you install SQL Server 2000 on a Win2K3 telling
you that you do not have SP3. Install the latest service pack after
installing SQL Server 2000
"zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
> Actually I personally am leaning more towards putting it on a w2k3 OS
> instead of w2k but am concerned if there would be anything in w2k3 that
> wouldn't support w2k as in the system files, ad/domain, etc? Like would
> you happen to know if there were anything that was left out in w2k3 that
> was in w2k?
> Thanks a bunch for your quick and helpful reply. Much appreciated
>
> "bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
> news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
>
|||I guess 2 main things that come to mind on that w2k server is that I've
installed a certificate from an ms ca service (in use for network ssl 'Force
protocol encryption' SQL Server Network Utility) in which I can just do
another certificate request/install and some .dll's that a VB app uses but I
would think that these shouldn't be an issue in that w2k3 would definitely
continue to support these. Will look into it further. Thanks so much for
your speedy informative reply. Will greatly help out in clearing things up
and expediting my research
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u$QuvTm3HHA.5724@.TK2MSFTNGP05.phx.gbl...
> Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just
> remember to ignore the warning when you install SQL Server 2000 on a
> Win2K3 telling you that you do not have SP3. Install the latest service
> pack after installing SQL Server 2000
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
>
|||Sorry if I'm over analyzing this perhaps but I can't seem to visualize some
of the "X" factors like how to keep the same server name, domain and IP
address the same after rebuilding/restoring the master db onto the new
machine since this holds the domain logins/jobs. Are there any websites
that can layout it out step by step in retiring an old w2k-sql2k and restore
it onto a newer machine with w2k3-sql2k?
Thanks for your helpful replies bass_player.
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u$QuvTm3HHA.5724@.TK2MSFTNGP05.phx.gbl...
> Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just
> remember to ignore the warning when you install SQL Server 2000 on a
> Win2K3 telling you that you do not have SP3. Install the latest service
> pack after installing SQL Server 2000
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
>
Would anyone know or recommend/advise the easiest approach in bringing down
and retiring an existing SQL2K running on W2K Server and brining it up with
all of the data, jobs, etc. onto a newer server machine? Wondering if there
was a way maybe do a full server restore from one of our server backup tapes
instead of having to reinstall/reconfigure everything from scratch.
Thanks in advance.
Imaging is one approach if you have an imaging software like StorageCraft or
Acronis. But a main consideration here is hardware and configuration. The
source and destination may have different disk configurations. Another
considertation maybe to use Win2K3 instead of Win2K. If what you're
intending to restore is simply SQL Server, just a backup of all system and
user database would be enough and a very good restore process
On the old SQL Server instance,
1) stop all applications accessing your SQL Server
2) backup all your system and user databases
3) identify the latest hotfix you have. This is necessary for you to
restore on the new one
On the new SQL Server instance,
1) Install SQL Server together with the service packs and hotfixes up to the
one you have on the old instance
2) start SQL Server in single-user mode using the sqlservr.exe -c -m
3) restore the master database and restart the SQL Server service
4) restore the msdb database - be sure the SQLAgent service is not runnig
before you do so
5) restore model database if necessary
6) reconfigure your tempdb if necessary
7) restore all user databases and reconfigure if necessary - file locations
in particular
"zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
> Hello,
> Would anyone know or recommend/advise the easiest approach in bringing
> down and retiring an existing SQL2K running on W2K Server and brining it
> up with all of the data, jobs, etc. onto a newer server machine?
> Wondering if there was a way maybe do a full server restore from one of
> our server backup tapes instead of having to reinstall/reconfigure
> everything from scratch.
> Thanks in advance.
>
|||Actually I personally am leaning more towards putting it on a w2k3 OS
instead of w2k but am concerned if there would be anything in w2k3 that
wouldn't support w2k as in the system files, ad/domain, etc? Like would you
happen to know if there were anything that was left out in w2k3 that was in
w2k?
Thanks a bunch for your quick and helpful reply. Much appreciated
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
> Imaging is one approach if you have an imaging software like StorageCraft
> or Acronis. But a main consideration here is hardware and configuration.
> The source and destination may have different disk configurations. Another
> considertation maybe to use Win2K3 instead of Win2K. If what you're
> intending to restore is simply SQL Server, just a backup of all system and
> user database would be enough and a very good restore process
> On the old SQL Server instance,
> 1) stop all applications accessing your SQL Server
> 2) backup all your system and user databases
> 3) identify the latest hotfix you have. This is necessary for you to
> restore on the new one
> On the new SQL Server instance,
> 1) Install SQL Server together with the service packs and hotfixes up to
> the one you have on the old instance
> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
> 3) restore the master database and restart the SQL Server service
> 4) restore the msdb database - be sure the SQLAgent service is not runnig
> before you do so
> 5) restore model database if necessary
> 6) reconfigure your tempdb if necessary
> 7) restore all user databases and reconfigure if necessary - file
> locations in particular
>
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>
|||Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just remember
to ignore the warning when you install SQL Server 2000 on a Win2K3 telling
you that you do not have SP3. Install the latest service pack after
installing SQL Server 2000
"zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
> Actually I personally am leaning more towards putting it on a w2k3 OS
> instead of w2k but am concerned if there would be anything in w2k3 that
> wouldn't support w2k as in the system files, ad/domain, etc? Like would
> you happen to know if there were anything that was left out in w2k3 that
> was in w2k?
> Thanks a bunch for your quick and helpful reply. Much appreciated
>
> "bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
> news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
>
|||I guess 2 main things that come to mind on that w2k server is that I've
installed a certificate from an ms ca service (in use for network ssl 'Force
protocol encryption' SQL Server Network Utility) in which I can just do
another certificate request/install and some .dll's that a VB app uses but I
would think that these shouldn't be an issue in that w2k3 would definitely
continue to support these. Will look into it further. Thanks so much for
your speedy informative reply. Will greatly help out in clearing things up
and expediting my research
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u$QuvTm3HHA.5724@.TK2MSFTNGP05.phx.gbl...
> Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just
> remember to ignore the warning when you install SQL Server 2000 on a
> Win2K3 telling you that you do not have SP3. Install the latest service
> pack after installing SQL Server 2000
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
>
|||Sorry if I'm over analyzing this perhaps but I can't seem to visualize some
of the "X" factors like how to keep the same server name, domain and IP
address the same after rebuilding/restoring the master db onto the new
machine since this holds the domain logins/jobs. Are there any websites
that can layout it out step by step in retiring an old w2k-sql2k and restore
it onto a newer machine with w2k3-sql2k?
Thanks for your helpful replies bass_player.
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u$QuvTm3HHA.5724@.TK2MSFTNGP05.phx.gbl...
> Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just
> remember to ignore the warning when you install SQL Server 2000 on a
> Win2K3 telling you that you do not have SP3. Install the latest service
> pack after installing SQL Server 2000
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
>
Restore SQL2K on different machine
Hello,
Would anyone know or recommend/advise the easiest approach in bringing down
and retiring an existing SQL2K running on W2K Server and brining it up with
all of the data, jobs, etc. onto a newer server machine? Wondering if there
was a way maybe do a full server restore from one of our server backup tapes
instead of having to reinstall/reconfigure everything from scratch.
Thanks in advance.Imaging is one approach if you have an imaging software like StorageCraft or
Acronis. But a main consideration here is hardware and configuration. The
source and destination may have different disk configurations. Another
considertation maybe to use Win2K3 instead of Win2K. If what you're
intending to restore is simply SQL Server, just a backup of all system and
user database would be enough and a very good restore process
On the old SQL Server instance,
1) stop all applications accessing your SQL Server
2) backup all your system and user databases
3) identify the latest hotfix you have. This is necessary for you to
restore on the new one
On the new SQL Server instance,
1) Install SQL Server together with the service packs and hotfixes up to the
one you have on the old instance
2) start SQL Server in single-user mode using the sqlservr.exe -c -m
3) restore the master database and restart the SQL Server service
4) restore the msdb database - be sure the SQLAgent service is not runnig
before you do so
5) restore model database if necessary
6) reconfigure your tempdb if necessary
7) restore all user databases and reconfigure if necessary - file locations
in particular
"zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
> Hello,
> Would anyone know or recommend/advise the easiest approach in bringing
> down and retiring an existing SQL2K running on W2K Server and brining it
> up with all of the data, jobs, etc. onto a newer server machine?
> Wondering if there was a way maybe do a full server restore from one of
> our server backup tapes instead of having to reinstall/reconfigure
> everything from scratch.
> Thanks in advance.
>|||Actually I personally am leaning more towards putting it on a w2k3 OS
instead of w2k but am concerned if there would be anything in w2k3 that
wouldn't support w2k as in the system files, ad/domain, etc? Like would you
happen to know if there were anything that was left out in w2k3 that was in
w2k?
Thanks a bunch for your quick and helpful reply. Much appreciated :)
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
> Imaging is one approach if you have an imaging software like StorageCraft
> or Acronis. But a main consideration here is hardware and configuration.
> The source and destination may have different disk configurations. Another
> considertation maybe to use Win2K3 instead of Win2K. If what you're
> intending to restore is simply SQL Server, just a backup of all system and
> user database would be enough and a very good restore process
> On the old SQL Server instance,
> 1) stop all applications accessing your SQL Server
> 2) backup all your system and user databases
> 3) identify the latest hotfix you have. This is necessary for you to
> restore on the new one
> On the new SQL Server instance,
> 1) Install SQL Server together with the service packs and hotfixes up to
> the one you have on the old instance
> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
> 3) restore the master database and restart the SQL Server service
> 4) restore the msdb database - be sure the SQLAgent service is not runnig
> before you do so
> 5) restore model database if necessary
> 6) reconfigure your tempdb if necessary
> 7) restore all user databases and reconfigure if necessary - file
> locations in particular
>
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>> Hello,
>> Would anyone know or recommend/advise the easiest approach in bringing
>> down and retiring an existing SQL2K running on W2K Server and brining it
>> up with all of the data, jobs, etc. onto a newer server machine?
>> Wondering if there was a way maybe do a full server restore from one of
>> our server backup tapes instead of having to reinstall/reconfigure
>> everything from scratch.
>> Thanks in advance.
>|||Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just remember
to ignore the warning when you install SQL Server 2000 on a Win2K3 telling
you that you do not have SP3. Install the latest service pack after
installing SQL Server 2000
"zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
> Actually I personally am leaning more towards putting it on a w2k3 OS
> instead of w2k but am concerned if there would be anything in w2k3 that
> wouldn't support w2k as in the system files, ad/domain, etc? Like would
> you happen to know if there were anything that was left out in w2k3 that
> was in w2k?
> Thanks a bunch for your quick and helpful reply. Much appreciated :)
>
> "bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
> news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
>> Imaging is one approach if you have an imaging software like StorageCraft
>> or Acronis. But a main consideration here is hardware and configuration.
>> The source and destination may have different disk configurations.
>> Another considertation maybe to use Win2K3 instead of Win2K. If what
>> you're intending to restore is simply SQL Server, just a backup of all
>> system and user database would be enough and a very good restore process
>> On the old SQL Server instance,
>> 1) stop all applications accessing your SQL Server
>> 2) backup all your system and user databases
>> 3) identify the latest hotfix you have. This is necessary for you to
>> restore on the new one
>> On the new SQL Server instance,
>> 1) Install SQL Server together with the service packs and hotfixes up to
>> the one you have on the old instance
>> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
>> 3) restore the master database and restart the SQL Server service
>> 4) restore the msdb database - be sure the SQLAgent service is not runnig
>> before you do so
>> 5) restore model database if necessary
>> 6) reconfigure your tempdb if necessary
>> 7) restore all user databases and reconfigure if necessary - file
>> locations in particular
>>
>> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
>> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>> Hello,
>> Would anyone know or recommend/advise the easiest approach in bringing
>> down and retiring an existing SQL2K running on W2K Server and brining it
>> up with all of the data, jobs, etc. onto a newer server machine?
>> Wondering if there was a way maybe do a full server restore from one of
>> our server backup tapes instead of having to reinstall/reconfigure
>> everything from scratch.
>> Thanks in advance.
>>
>|||I guess 2 main things that come to mind on that w2k server is that I've
installed a certificate from an ms ca service (in use for network ssl 'Force
protocol encryption' SQL Server Network Utility) in which I can just do
another certificate request/install and some .dll's that a VB app uses but I
would think that these shouldn't be an issue in that w2k3 would definitely
continue to support these. Will look into it further. Thanks so much for
your speedy informative reply. Will greatly help out in clearing things up
and expediting my research :)
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u$QuvTm3HHA.5724@.TK2MSFTNGP05.phx.gbl...
> Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just
> remember to ignore the warning when you install SQL Server 2000 on a
> Win2K3 telling you that you do not have SP3. Install the latest service
> pack after installing SQL Server 2000
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
>> Actually I personally am leaning more towards putting it on a w2k3 OS
>> instead of w2k but am concerned if there would be anything in w2k3 that
>> wouldn't support w2k as in the system files, ad/domain, etc? Like would
>> you happen to know if there were anything that was left out in w2k3 that
>> was in w2k?
>> Thanks a bunch for your quick and helpful reply. Much appreciated :)
>>
>> "bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
>> news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
>> Imaging is one approach if you have an imaging software like
>> StorageCraft or Acronis. But a main consideration here is hardware and
>> configuration. The source and destination may have different disk
>> configurations. Another considertation maybe to use Win2K3 instead of
>> Win2K. If what you're intending to restore is simply SQL Server, just a
>> backup of all system and user database would be enough and a very good
>> restore process
>> On the old SQL Server instance,
>> 1) stop all applications accessing your SQL Server
>> 2) backup all your system and user databases
>> 3) identify the latest hotfix you have. This is necessary for you to
>> restore on the new one
>> On the new SQL Server instance,
>> 1) Install SQL Server together with the service packs and hotfixes up to
>> the one you have on the old instance
>> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
>> 3) restore the master database and restart the SQL Server service
>> 4) restore the msdb database - be sure the SQLAgent service is not
>> runnig before you do so
>> 5) restore model database if necessary
>> 6) reconfigure your tempdb if necessary
>> 7) restore all user databases and reconfigure if necessary - file
>> locations in particular
>>
>> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
>> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>> Hello,
>> Would anyone know or recommend/advise the easiest approach in bringing
>> down and retiring an existing SQL2K running on W2K Server and brining
>> it up with all of the data, jobs, etc. onto a newer server machine?
>> Wondering if there was a way maybe do a full server restore from one of
>> our server backup tapes instead of having to reinstall/reconfigure
>> everything from scratch.
>> Thanks in advance.
>>
>>
>|||Sorry if I'm over analyzing this perhaps but I can't seem to visualize some
of the "X" factors like how to keep the same server name, domain and IP
address the same after rebuilding/restoring the master db onto the new
machine since this holds the domain logins/jobs. Are there any websites
that can layout it out step by step in retiring an old w2k-sql2k and restore
it onto a newer machine with w2k3-sql2k?
Thanks for your helpful replies bass_player.
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u$QuvTm3HHA.5724@.TK2MSFTNGP05.phx.gbl...
> Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just
> remember to ignore the warning when you install SQL Server 2000 on a
> Win2K3 telling you that you do not have SP3. Install the latest service
> pack after installing SQL Server 2000
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
>> Actually I personally am leaning more towards putting it on a w2k3 OS
>> instead of w2k but am concerned if there would be anything in w2k3 that
>> wouldn't support w2k as in the system files, ad/domain, etc? Like would
>> you happen to know if there were anything that was left out in w2k3 that
>> was in w2k?
>> Thanks a bunch for your quick and helpful reply. Much appreciated :)
>>
>> "bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
>> news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
>> Imaging is one approach if you have an imaging software like
>> StorageCraft or Acronis. But a main consideration here is hardware and
>> configuration. The source and destination may have different disk
>> configurations. Another considertation maybe to use Win2K3 instead of
>> Win2K. If what you're intending to restore is simply SQL Server, just a
>> backup of all system and user database would be enough and a very good
>> restore process
>> On the old SQL Server instance,
>> 1) stop all applications accessing your SQL Server
>> 2) backup all your system and user databases
>> 3) identify the latest hotfix you have. This is necessary for you to
>> restore on the new one
>> On the new SQL Server instance,
>> 1) Install SQL Server together with the service packs and hotfixes up to
>> the one you have on the old instance
>> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
>> 3) restore the master database and restart the SQL Server service
>> 4) restore the msdb database - be sure the SQLAgent service is not
>> runnig before you do so
>> 5) restore model database if necessary
>> 6) reconfigure your tempdb if necessary
>> 7) restore all user databases and reconfigure if necessary - file
>> locations in particular
>>
>> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
>> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>> Hello,
>> Would anyone know or recommend/advise the easiest approach in bringing
>> down and retiring an existing SQL2K running on W2K Server and brining
>> it up with all of the data, jobs, etc. onto a newer server machine?
>> Wondering if there was a way maybe do a full server restore from one of
>> our server backup tapes instead of having to reinstall/reconfigure
>> everything from scratch.
>> Thanks in advance.
>>
>>
>|||Just a quick question in that did you mean w2k3 SP2 instead of SP3? My
coworker the network admin had w2k3 SP1 currently installed on our new
server and was wondering if he should go ahead and install SP2 which then
I'll install the sql2k or should I install sql2k first and then let him
install w2k3 SP2 and the rest of the windows updates?
Thanks again bass_player.
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u$QuvTm3HHA.5724@.TK2MSFTNGP05.phx.gbl...
> Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just
> remember to ignore the warning when you install SQL Server 2000 on a
> Win2K3 telling you that you do not have SP3. Install the latest service
> pack after installing SQL Server 2000
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
>> Actually I personally am leaning more towards putting it on a w2k3 OS
>> instead of w2k but am concerned if there would be anything in w2k3 that
>> wouldn't support w2k as in the system files, ad/domain, etc? Like would
>> you happen to know if there were anything that was left out in w2k3 that
>> was in w2k?
>> Thanks a bunch for your quick and helpful reply. Much appreciated :)
>>
>> "bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
>> news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
>> Imaging is one approach if you have an imaging software like
>> StorageCraft or Acronis. But a main consideration here is hardware and
>> configuration. The source and destination may have different disk
>> configurations. Another considertation maybe to use Win2K3 instead of
>> Win2K. If what you're intending to restore is simply SQL Server, just a
>> backup of all system and user database would be enough and a very good
>> restore process
>> On the old SQL Server instance,
>> 1) stop all applications accessing your SQL Server
>> 2) backup all your system and user databases
>> 3) identify the latest hotfix you have. This is necessary for you to
>> restore on the new one
>> On the new SQL Server instance,
>> 1) Install SQL Server together with the service packs and hotfixes up to
>> the one you have on the old instance
>> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
>> 3) restore the master database and restart the SQL Server service
>> 4) restore the msdb database - be sure the SQLAgent service is not
>> runnig before you do so
>> 5) restore model database if necessary
>> 6) reconfigure your tempdb if necessary
>> 7) restore all user databases and reconfigure if necessary - file
>> locations in particular
>>
>> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
>> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>> Hello,
>> Would anyone know or recommend/advise the easiest approach in bringing
>> down and retiring an existing SQL2K running on W2K Server and brining
>> it up with all of the data, jobs, etc. onto a newer server machine?
>> Wondering if there was a way maybe do a full server restore from one of
>> our server backup tapes instead of having to reinstall/reconfigure
>> everything from scratch.
>> Thanks in advance.
>>
>>
>sql
Would anyone know or recommend/advise the easiest approach in bringing down
and retiring an existing SQL2K running on W2K Server and brining it up with
all of the data, jobs, etc. onto a newer server machine? Wondering if there
was a way maybe do a full server restore from one of our server backup tapes
instead of having to reinstall/reconfigure everything from scratch.
Thanks in advance.Imaging is one approach if you have an imaging software like StorageCraft or
Acronis. But a main consideration here is hardware and configuration. The
source and destination may have different disk configurations. Another
considertation maybe to use Win2K3 instead of Win2K. If what you're
intending to restore is simply SQL Server, just a backup of all system and
user database would be enough and a very good restore process
On the old SQL Server instance,
1) stop all applications accessing your SQL Server
2) backup all your system and user databases
3) identify the latest hotfix you have. This is necessary for you to
restore on the new one
On the new SQL Server instance,
1) Install SQL Server together with the service packs and hotfixes up to the
one you have on the old instance
2) start SQL Server in single-user mode using the sqlservr.exe -c -m
3) restore the master database and restart the SQL Server service
4) restore the msdb database - be sure the SQLAgent service is not runnig
before you do so
5) restore model database if necessary
6) reconfigure your tempdb if necessary
7) restore all user databases and reconfigure if necessary - file locations
in particular
"zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
> Hello,
> Would anyone know or recommend/advise the easiest approach in bringing
> down and retiring an existing SQL2K running on W2K Server and brining it
> up with all of the data, jobs, etc. onto a newer server machine?
> Wondering if there was a way maybe do a full server restore from one of
> our server backup tapes instead of having to reinstall/reconfigure
> everything from scratch.
> Thanks in advance.
>|||Actually I personally am leaning more towards putting it on a w2k3 OS
instead of w2k but am concerned if there would be anything in w2k3 that
wouldn't support w2k as in the system files, ad/domain, etc? Like would you
happen to know if there were anything that was left out in w2k3 that was in
w2k?
Thanks a bunch for your quick and helpful reply. Much appreciated :)
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
> Imaging is one approach if you have an imaging software like StorageCraft
> or Acronis. But a main consideration here is hardware and configuration.
> The source and destination may have different disk configurations. Another
> considertation maybe to use Win2K3 instead of Win2K. If what you're
> intending to restore is simply SQL Server, just a backup of all system and
> user database would be enough and a very good restore process
> On the old SQL Server instance,
> 1) stop all applications accessing your SQL Server
> 2) backup all your system and user databases
> 3) identify the latest hotfix you have. This is necessary for you to
> restore on the new one
> On the new SQL Server instance,
> 1) Install SQL Server together with the service packs and hotfixes up to
> the one you have on the old instance
> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
> 3) restore the master database and restart the SQL Server service
> 4) restore the msdb database - be sure the SQLAgent service is not runnig
> before you do so
> 5) restore model database if necessary
> 6) reconfigure your tempdb if necessary
> 7) restore all user databases and reconfigure if necessary - file
> locations in particular
>
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>> Hello,
>> Would anyone know or recommend/advise the easiest approach in bringing
>> down and retiring an existing SQL2K running on W2K Server and brining it
>> up with all of the data, jobs, etc. onto a newer server machine?
>> Wondering if there was a way maybe do a full server restore from one of
>> our server backup tapes instead of having to reinstall/reconfigure
>> everything from scratch.
>> Thanks in advance.
>|||Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just remember
to ignore the warning when you install SQL Server 2000 on a Win2K3 telling
you that you do not have SP3. Install the latest service pack after
installing SQL Server 2000
"zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
> Actually I personally am leaning more towards putting it on a w2k3 OS
> instead of w2k but am concerned if there would be anything in w2k3 that
> wouldn't support w2k as in the system files, ad/domain, etc? Like would
> you happen to know if there were anything that was left out in w2k3 that
> was in w2k?
> Thanks a bunch for your quick and helpful reply. Much appreciated :)
>
> "bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
> news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
>> Imaging is one approach if you have an imaging software like StorageCraft
>> or Acronis. But a main consideration here is hardware and configuration.
>> The source and destination may have different disk configurations.
>> Another considertation maybe to use Win2K3 instead of Win2K. If what
>> you're intending to restore is simply SQL Server, just a backup of all
>> system and user database would be enough and a very good restore process
>> On the old SQL Server instance,
>> 1) stop all applications accessing your SQL Server
>> 2) backup all your system and user databases
>> 3) identify the latest hotfix you have. This is necessary for you to
>> restore on the new one
>> On the new SQL Server instance,
>> 1) Install SQL Server together with the service packs and hotfixes up to
>> the one you have on the old instance
>> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
>> 3) restore the master database and restart the SQL Server service
>> 4) restore the msdb database - be sure the SQLAgent service is not runnig
>> before you do so
>> 5) restore model database if necessary
>> 6) reconfigure your tempdb if necessary
>> 7) restore all user databases and reconfigure if necessary - file
>> locations in particular
>>
>> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
>> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>> Hello,
>> Would anyone know or recommend/advise the easiest approach in bringing
>> down and retiring an existing SQL2K running on W2K Server and brining it
>> up with all of the data, jobs, etc. onto a newer server machine?
>> Wondering if there was a way maybe do a full server restore from one of
>> our server backup tapes instead of having to reinstall/reconfigure
>> everything from scratch.
>> Thanks in advance.
>>
>|||I guess 2 main things that come to mind on that w2k server is that I've
installed a certificate from an ms ca service (in use for network ssl 'Force
protocol encryption' SQL Server Network Utility) in which I can just do
another certificate request/install and some .dll's that a VB app uses but I
would think that these shouldn't be an issue in that w2k3 would definitely
continue to support these. Will look into it further. Thanks so much for
your speedy informative reply. Will greatly help out in clearing things up
and expediting my research :)
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u$QuvTm3HHA.5724@.TK2MSFTNGP05.phx.gbl...
> Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just
> remember to ignore the warning when you install SQL Server 2000 on a
> Win2K3 telling you that you do not have SP3. Install the latest service
> pack after installing SQL Server 2000
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
>> Actually I personally am leaning more towards putting it on a w2k3 OS
>> instead of w2k but am concerned if there would be anything in w2k3 that
>> wouldn't support w2k as in the system files, ad/domain, etc? Like would
>> you happen to know if there were anything that was left out in w2k3 that
>> was in w2k?
>> Thanks a bunch for your quick and helpful reply. Much appreciated :)
>>
>> "bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
>> news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
>> Imaging is one approach if you have an imaging software like
>> StorageCraft or Acronis. But a main consideration here is hardware and
>> configuration. The source and destination may have different disk
>> configurations. Another considertation maybe to use Win2K3 instead of
>> Win2K. If what you're intending to restore is simply SQL Server, just a
>> backup of all system and user database would be enough and a very good
>> restore process
>> On the old SQL Server instance,
>> 1) stop all applications accessing your SQL Server
>> 2) backup all your system and user databases
>> 3) identify the latest hotfix you have. This is necessary for you to
>> restore on the new one
>> On the new SQL Server instance,
>> 1) Install SQL Server together with the service packs and hotfixes up to
>> the one you have on the old instance
>> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
>> 3) restore the master database and restart the SQL Server service
>> 4) restore the msdb database - be sure the SQLAgent service is not
>> runnig before you do so
>> 5) restore model database if necessary
>> 6) reconfigure your tempdb if necessary
>> 7) restore all user databases and reconfigure if necessary - file
>> locations in particular
>>
>> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
>> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>> Hello,
>> Would anyone know or recommend/advise the easiest approach in bringing
>> down and retiring an existing SQL2K running on W2K Server and brining
>> it up with all of the data, jobs, etc. onto a newer server machine?
>> Wondering if there was a way maybe do a full server restore from one of
>> our server backup tapes instead of having to reinstall/reconfigure
>> everything from scratch.
>> Thanks in advance.
>>
>>
>|||Sorry if I'm over analyzing this perhaps but I can't seem to visualize some
of the "X" factors like how to keep the same server name, domain and IP
address the same after rebuilding/restoring the master db onto the new
machine since this holds the domain logins/jobs. Are there any websites
that can layout it out step by step in retiring an old w2k-sql2k and restore
it onto a newer machine with w2k3-sql2k?
Thanks for your helpful replies bass_player.
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u$QuvTm3HHA.5724@.TK2MSFTNGP05.phx.gbl...
> Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just
> remember to ignore the warning when you install SQL Server 2000 on a
> Win2K3 telling you that you do not have SP3. Install the latest service
> pack after installing SQL Server 2000
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
>> Actually I personally am leaning more towards putting it on a w2k3 OS
>> instead of w2k but am concerned if there would be anything in w2k3 that
>> wouldn't support w2k as in the system files, ad/domain, etc? Like would
>> you happen to know if there were anything that was left out in w2k3 that
>> was in w2k?
>> Thanks a bunch for your quick and helpful reply. Much appreciated :)
>>
>> "bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
>> news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
>> Imaging is one approach if you have an imaging software like
>> StorageCraft or Acronis. But a main consideration here is hardware and
>> configuration. The source and destination may have different disk
>> configurations. Another considertation maybe to use Win2K3 instead of
>> Win2K. If what you're intending to restore is simply SQL Server, just a
>> backup of all system and user database would be enough and a very good
>> restore process
>> On the old SQL Server instance,
>> 1) stop all applications accessing your SQL Server
>> 2) backup all your system and user databases
>> 3) identify the latest hotfix you have. This is necessary for you to
>> restore on the new one
>> On the new SQL Server instance,
>> 1) Install SQL Server together with the service packs and hotfixes up to
>> the one you have on the old instance
>> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
>> 3) restore the master database and restart the SQL Server service
>> 4) restore the msdb database - be sure the SQLAgent service is not
>> runnig before you do so
>> 5) restore model database if necessary
>> 6) reconfigure your tempdb if necessary
>> 7) restore all user databases and reconfigure if necessary - file
>> locations in particular
>>
>> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
>> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>> Hello,
>> Would anyone know or recommend/advise the easiest approach in bringing
>> down and retiring an existing SQL2K running on W2K Server and brining
>> it up with all of the data, jobs, etc. onto a newer server machine?
>> Wondering if there was a way maybe do a full server restore from one of
>> our server backup tapes instead of having to reinstall/reconfigure
>> everything from scratch.
>> Thanks in advance.
>>
>>
>|||Just a quick question in that did you mean w2k3 SP2 instead of SP3? My
coworker the network admin had w2k3 SP1 currently installed on our new
server and was wondering if he should go ahead and install SP2 which then
I'll install the sql2k or should I install sql2k first and then let him
install w2k3 SP2 and the rest of the windows updates?
Thanks again bass_player.
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u$QuvTm3HHA.5724@.TK2MSFTNGP05.phx.gbl...
> Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just
> remember to ignore the warning when you install SQL Server 2000 on a
> Win2K3 telling you that you do not have SP3. Install the latest service
> pack after installing SQL Server 2000
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
>> Actually I personally am leaning more towards putting it on a w2k3 OS
>> instead of w2k but am concerned if there would be anything in w2k3 that
>> wouldn't support w2k as in the system files, ad/domain, etc? Like would
>> you happen to know if there were anything that was left out in w2k3 that
>> was in w2k?
>> Thanks a bunch for your quick and helpful reply. Much appreciated :)
>>
>> "bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
>> news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
>> Imaging is one approach if you have an imaging software like
>> StorageCraft or Acronis. But a main consideration here is hardware and
>> configuration. The source and destination may have different disk
>> configurations. Another considertation maybe to use Win2K3 instead of
>> Win2K. If what you're intending to restore is simply SQL Server, just a
>> backup of all system and user database would be enough and a very good
>> restore process
>> On the old SQL Server instance,
>> 1) stop all applications accessing your SQL Server
>> 2) backup all your system and user databases
>> 3) identify the latest hotfix you have. This is necessary for you to
>> restore on the new one
>> On the new SQL Server instance,
>> 1) Install SQL Server together with the service packs and hotfixes up to
>> the one you have on the old instance
>> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
>> 3) restore the master database and restart the SQL Server service
>> 4) restore the msdb database - be sure the SQLAgent service is not
>> runnig before you do so
>> 5) restore model database if necessary
>> 6) reconfigure your tempdb if necessary
>> 7) restore all user databases and reconfigure if necessary - file
>> locations in particular
>>
>> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
>> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>> Hello,
>> Would anyone know or recommend/advise the easiest approach in bringing
>> down and retiring an existing SQL2K running on W2K Server and brining
>> it up with all of the data, jobs, etc. onto a newer server machine?
>> Wondering if there was a way maybe do a full server restore from one of
>> our server backup tapes instead of having to reinstall/reconfigure
>> everything from scratch.
>> Thanks in advance.
>>
>>
>sql
Restore SQL Server to default SQL data directory
Hi,
I need to prepare an Installshield project that restore a database on
my target machine.
No problem with script
RESTORE DATABASE BIGStudio FROM DISK=MyDir\MyBackup.bak'
WITH FILE = 1, NOUNLOAD, REPLACE, STATS = 10, MOVE 'DB_dat' TO
'\Data\DB_Data.mdf',
MOVE 'DB__log' TO '\Data\DB_log.ldf'.
But in my target machine I can have SQL Server 2000, SQL Server 2005,
MSDE 2000...
I've tried to restore DB on my INSTALL dir but I receive an access
denied error. How can I restore my DB to the default SQL Server data
directory on my target machine?
Thank you
Gianluca DhoYou may need to obtain this info dynamically?
Check out xp_instance_regread
Immy
"Gianluca Dho" <gianluca.dho@.gmail.com> wrote in message
news:1159535209.992156.163070@.b28g2000cwb.googlegroups.com...
> Hi,
> I need to prepare an Installshield project that restore a database on
> my target machine.
> No problem with script
> RESTORE DATABASE BIGStudio FROM DISK=MyDir\MyBackup.bak'
> WITH FILE = 1, NOUNLOAD, REPLACE, STATS = 10, MOVE 'DB_dat' TO
> '\Data\DB_Data.mdf',
> MOVE 'DB__log' TO '\Data\DB_log.ldf'.
> But in my target machine I can have SQL Server 2000, SQL Server 2005,
> MSDE 2000...
> I've tried to restore DB on my INSTALL dir but I receive an access
> denied error. How can I restore my DB to the default SQL Server data
> directory on my target machine?
> Thank you
> Gianluca Dho
>
I need to prepare an Installshield project that restore a database on
my target machine.
No problem with script
RESTORE DATABASE BIGStudio FROM DISK=MyDir\MyBackup.bak'
WITH FILE = 1, NOUNLOAD, REPLACE, STATS = 10, MOVE 'DB_dat' TO
'\Data\DB_Data.mdf',
MOVE 'DB__log' TO '\Data\DB_log.ldf'.
But in my target machine I can have SQL Server 2000, SQL Server 2005,
MSDE 2000...
I've tried to restore DB on my INSTALL dir but I receive an access
denied error. How can I restore my DB to the default SQL Server data
directory on my target machine?
Thank you
Gianluca DhoYou may need to obtain this info dynamically?
Check out xp_instance_regread
Immy
"Gianluca Dho" <gianluca.dho@.gmail.com> wrote in message
news:1159535209.992156.163070@.b28g2000cwb.googlegroups.com...
> Hi,
> I need to prepare an Installshield project that restore a database on
> my target machine.
> No problem with script
> RESTORE DATABASE BIGStudio FROM DISK=MyDir\MyBackup.bak'
> WITH FILE = 1, NOUNLOAD, REPLACE, STATS = 10, MOVE 'DB_dat' TO
> '\Data\DB_Data.mdf',
> MOVE 'DB__log' TO '\Data\DB_log.ldf'.
> But in my target machine I can have SQL Server 2000, SQL Server 2005,
> MSDE 2000...
> I've tried to restore DB on my INSTALL dir but I receive an access
> denied error. How can I restore my DB to the default SQL Server data
> directory on my target machine?
> Thank you
> Gianluca Dho
>
Restore SQL Server to default SQL data directory
Hi,
I need to prepare an Installshield project that restore a database on
my target machine.
No problem with script
RESTORE DATABASE BIGStudio FROM DISK=MyDir\MyBackup.bak'
WITH FILE = 1, NOUNLOAD, REPLACE, STATS = 10, MOVE 'DB_dat' TO
'\Data\DB_Data.mdf',
MOVE 'DB__log' TO '\Data\DB_log.ldf'.
But in my target machine I can have SQL Server 2000, SQL Server 2005,
MSDE 2000...
I've tried to restore DB on my INSTALL dir but I receive an access
denied error. How can I restore my DB to the default SQL Server data
directory on my target machine?
Thank you
Gianluca Dho
You may need to obtain this info dynamically?
Check out xp_instance_regread
Immy
"Gianluca Dho" <gianluca.dho@.gmail.com> wrote in message
news:1159535209.992156.163070@.b28g2000cwb.googlegr oups.com...
> Hi,
> I need to prepare an Installshield project that restore a database on
> my target machine.
> No problem with script
> RESTORE DATABASE BIGStudio FROM DISK=MyDir\MyBackup.bak'
> WITH FILE = 1, NOUNLOAD, REPLACE, STATS = 10, MOVE 'DB_dat' TO
> '\Data\DB_Data.mdf',
> MOVE 'DB__log' TO '\Data\DB_log.ldf'.
> But in my target machine I can have SQL Server 2000, SQL Server 2005,
> MSDE 2000...
> I've tried to restore DB on my INSTALL dir but I receive an access
> denied error. How can I restore my DB to the default SQL Server data
> directory on my target machine?
> Thank you
> Gianluca Dho
>
sql
I need to prepare an Installshield project that restore a database on
my target machine.
No problem with script
RESTORE DATABASE BIGStudio FROM DISK=MyDir\MyBackup.bak'
WITH FILE = 1, NOUNLOAD, REPLACE, STATS = 10, MOVE 'DB_dat' TO
'\Data\DB_Data.mdf',
MOVE 'DB__log' TO '\Data\DB_log.ldf'.
But in my target machine I can have SQL Server 2000, SQL Server 2005,
MSDE 2000...
I've tried to restore DB on my INSTALL dir but I receive an access
denied error. How can I restore my DB to the default SQL Server data
directory on my target machine?
Thank you
Gianluca Dho
You may need to obtain this info dynamically?
Check out xp_instance_regread
Immy
"Gianluca Dho" <gianluca.dho@.gmail.com> wrote in message
news:1159535209.992156.163070@.b28g2000cwb.googlegr oups.com...
> Hi,
> I need to prepare an Installshield project that restore a database on
> my target machine.
> No problem with script
> RESTORE DATABASE BIGStudio FROM DISK=MyDir\MyBackup.bak'
> WITH FILE = 1, NOUNLOAD, REPLACE, STATS = 10, MOVE 'DB_dat' TO
> '\Data\DB_Data.mdf',
> MOVE 'DB__log' TO '\Data\DB_log.ldf'.
> But in my target machine I can have SQL Server 2000, SQL Server 2005,
> MSDE 2000...
> I've tried to restore DB on my INSTALL dir but I receive an access
> denied error. How can I restore my DB to the default SQL Server data
> directory on my target machine?
> Thank you
> Gianluca Dho
>
sql
Restore SQL Server to default SQL data directory
Hi,
I need to prepare an Installshield project that restore a database on
my target machine.
No problem with script
RESTORE DATABASE BIGStudio FROM DISK=MyDir\MyBackup.bak'
WITH FILE = 1, NOUNLOAD, REPLACE, STATS = 10, MOVE 'DB_dat' TO
'\Data\DB_Data.mdf',
MOVE 'DB__log' TO '\Data\DB_log.ldf'.
But in my target machine I can have SQL Server 2000, SQL Server 2005,
MSDE 2000...
I've tried to restore DB on my INSTALL dir but I receive an access
denied error. How can I restore my DB to the default SQL Server data
directory on my target machine?
Thank you
Gianluca DhoYou may need to obtain this info dynamically?
Check out xp_instance_regread
Immy
"Gianluca Dho" <gianluca.dho@.gmail.com> wrote in message
news:1159535209.992156.163070@.b28g2000cwb.googlegroups.com...
> Hi,
> I need to prepare an Installshield project that restore a database on
> my target machine.
> No problem with script
> RESTORE DATABASE BIGStudio FROM DISK=MyDir\MyBackup.bak'
> WITH FILE = 1, NOUNLOAD, REPLACE, STATS = 10, MOVE 'DB_dat' TO
> '\Data\DB_Data.mdf',
> MOVE 'DB__log' TO '\Data\DB_log.ldf'.
> But in my target machine I can have SQL Server 2000, SQL Server 2005,
> MSDE 2000...
> I've tried to restore DB on my INSTALL dir but I receive an access
> denied error. How can I restore my DB to the default SQL Server data
> directory on my target machine?
> Thank you
> Gianluca Dho
>
I need to prepare an Installshield project that restore a database on
my target machine.
No problem with script
RESTORE DATABASE BIGStudio FROM DISK=MyDir\MyBackup.bak'
WITH FILE = 1, NOUNLOAD, REPLACE, STATS = 10, MOVE 'DB_dat' TO
'\Data\DB_Data.mdf',
MOVE 'DB__log' TO '\Data\DB_log.ldf'.
But in my target machine I can have SQL Server 2000, SQL Server 2005,
MSDE 2000...
I've tried to restore DB on my INSTALL dir but I receive an access
denied error. How can I restore my DB to the default SQL Server data
directory on my target machine?
Thank you
Gianluca DhoYou may need to obtain this info dynamically?
Check out xp_instance_regread
Immy
"Gianluca Dho" <gianluca.dho@.gmail.com> wrote in message
news:1159535209.992156.163070@.b28g2000cwb.googlegroups.com...
> Hi,
> I need to prepare an Installshield project that restore a database on
> my target machine.
> No problem with script
> RESTORE DATABASE BIGStudio FROM DISK=MyDir\MyBackup.bak'
> WITH FILE = 1, NOUNLOAD, REPLACE, STATS = 10, MOVE 'DB_dat' TO
> '\Data\DB_Data.mdf',
> MOVE 'DB__log' TO '\Data\DB_log.ldf'.
> But in my target machine I can have SQL Server 2000, SQL Server 2005,
> MSDE 2000...
> I've tried to restore DB on my INSTALL dir but I receive an access
> denied error. How can I restore my DB to the default SQL Server data
> directory on my target machine?
> Thank you
> Gianluca Dho
>
Wednesday, March 21, 2012
Restore SQL 2000 different domain?
Hello. Would anyone know of the most advisable method in moving our SQL
2000 on ServerA to another SQL 2000 machine ServerB where we plan on
retiring ServerA and ServerB will take on the same name and IP address as
ServerA? I'm mainly wondering since we have some windows authentication
logins on our SQL Server and moving it to a different domain/machine would
affect anything.
Thanks in advance.
J
Hi
"J" wrote:
> Hello. Would anyone know of the most advisable method in moving our SQL
> 2000 on ServerA to another SQL 2000 machine ServerB where we plan on
> retiring ServerA and ServerB will take on the same name and IP address as
> ServerA? I'm mainly wondering since we have some windows authentication
> logins on our SQL Server and moving it to a different domain/machine would
> affect anything.
>
See http://support.microsoft.com/kb/246133/ on how to transfer logins from
one server to another.
If you rename the server you will need to drop it and re-add it. See
http://support.microsoft.com/kb/303774/
General information about moving databases see
http://support.microsoft.com/kb/314546
> Thanks in advance.
> J
John
|||Thanks for the info. Much appreciated.
Take care.
J
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:FC96D7E6-AEC9-4CC7-8602-75B61F1F571E@.microsoft.com...
> Hi
> "J" wrote:
> See http://support.microsoft.com/kb/246133/ on how to transfer logins from
> one server to another.
> If you rename the server you will need to drop it and re-add it. See
> http://support.microsoft.com/kb/303774/
> General information about moving databases see
> http://support.microsoft.com/kb/314546
>
> John
2000 on ServerA to another SQL 2000 machine ServerB where we plan on
retiring ServerA and ServerB will take on the same name and IP address as
ServerA? I'm mainly wondering since we have some windows authentication
logins on our SQL Server and moving it to a different domain/machine would
affect anything.
Thanks in advance.
J
Hi
"J" wrote:
> Hello. Would anyone know of the most advisable method in moving our SQL
> 2000 on ServerA to another SQL 2000 machine ServerB where we plan on
> retiring ServerA and ServerB will take on the same name and IP address as
> ServerA? I'm mainly wondering since we have some windows authentication
> logins on our SQL Server and moving it to a different domain/machine would
> affect anything.
>
See http://support.microsoft.com/kb/246133/ on how to transfer logins from
one server to another.
If you rename the server you will need to drop it and re-add it. See
http://support.microsoft.com/kb/303774/
General information about moving databases see
http://support.microsoft.com/kb/314546
> Thanks in advance.
> J
John
|||Thanks for the info. Much appreciated.
Take care.
J
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:FC96D7E6-AEC9-4CC7-8602-75B61F1F571E@.microsoft.com...
> Hi
> "J" wrote:
> See http://support.microsoft.com/kb/246133/ on how to transfer logins from
> one server to another.
> If you rename the server you will need to drop it and re-add it. See
> http://support.microsoft.com/kb/303774/
> General information about moving databases see
> http://support.microsoft.com/kb/314546
>
> John
Restore SQL 2000 different domain?
Hello. Would anyone know of the most advisable method in moving our SQL
2000 on ServerA to another SQL 2000 machine ServerB where we plan on
retiring ServerA and ServerB will take on the same name and IP address as
ServerA? I'm mainly wondering since we have some windows authentication
logins on our SQL Server and moving it to a different domain/machine would
affect anything.
Thanks in advance.
JHi
"J" wrote:
> Hello. Would anyone know of the most advisable method in moving our SQL
> 2000 on ServerA to another SQL 2000 machine ServerB where we plan on
> retiring ServerA and ServerB will take on the same name and IP address as
> ServerA? I'm mainly wondering since we have some windows authentication
> logins on our SQL Server and moving it to a different domain/machine would
> affect anything.
>
See http://support.microsoft.com/kb/246133/ on how to transfer logins from
one server to another.
If you rename the server you will need to drop it and re-add it. See
http://support.microsoft.com/kb/303774/
General information about moving databases see
http://support.microsoft.com/kb/314546
> Thanks in advance.
> J
John|||Thanks for the info. Much appreciated.
Take care.
J
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:FC96D7E6-AEC9-4CC7-8602-75B61F1F571E@.microsoft.com...
> Hi
> "J" wrote:
>> Hello. Would anyone know of the most advisable method in moving our SQL
>> 2000 on ServerA to another SQL 2000 machine ServerB where we plan on
>> retiring ServerA and ServerB will take on the same name and IP address as
>> ServerA? I'm mainly wondering since we have some windows authentication
>> logins on our SQL Server and moving it to a different domain/machine
>> would
>> affect anything.
> See http://support.microsoft.com/kb/246133/ on how to transfer logins from
> one server to another.
> If you rename the server you will need to drop it and re-add it. See
> http://support.microsoft.com/kb/303774/
> General information about moving databases see
> http://support.microsoft.com/kb/314546
>> Thanks in advance.
>> J
> John
2000 on ServerA to another SQL 2000 machine ServerB where we plan on
retiring ServerA and ServerB will take on the same name and IP address as
ServerA? I'm mainly wondering since we have some windows authentication
logins on our SQL Server and moving it to a different domain/machine would
affect anything.
Thanks in advance.
JHi
"J" wrote:
> Hello. Would anyone know of the most advisable method in moving our SQL
> 2000 on ServerA to another SQL 2000 machine ServerB where we plan on
> retiring ServerA and ServerB will take on the same name and IP address as
> ServerA? I'm mainly wondering since we have some windows authentication
> logins on our SQL Server and moving it to a different domain/machine would
> affect anything.
>
See http://support.microsoft.com/kb/246133/ on how to transfer logins from
one server to another.
If you rename the server you will need to drop it and re-add it. See
http://support.microsoft.com/kb/303774/
General information about moving databases see
http://support.microsoft.com/kb/314546
> Thanks in advance.
> J
John|||Thanks for the info. Much appreciated.
Take care.
J
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:FC96D7E6-AEC9-4CC7-8602-75B61F1F571E@.microsoft.com...
> Hi
> "J" wrote:
>> Hello. Would anyone know of the most advisable method in moving our SQL
>> 2000 on ServerA to another SQL 2000 machine ServerB where we plan on
>> retiring ServerA and ServerB will take on the same name and IP address as
>> ServerA? I'm mainly wondering since we have some windows authentication
>> logins on our SQL Server and moving it to a different domain/machine
>> would
>> affect anything.
> See http://support.microsoft.com/kb/246133/ on how to transfer logins from
> one server to another.
> If you rename the server you will need to drop it and re-add it. See
> http://support.microsoft.com/kb/303774/
> General information about moving databases see
> http://support.microsoft.com/kb/314546
>> Thanks in advance.
>> J
> John
Restore SQL 2000 different domain?
Hello. Would anyone know of the most advisable method in moving our SQL
2000 on ServerA to another SQL 2000 machine ServerB where we plan on
retiring ServerA and ServerB will take on the same name and IP address as
ServerA? I'm mainly wondering since we have some windows authentication
logins on our SQL Server and moving it to a different domain/machine would
affect anything.
Thanks in advance.
JHi
"J" wrote:
> Hello. Would anyone know of the most advisable method in moving our SQL
> 2000 on ServerA to another SQL 2000 machine ServerB where we plan on
> retiring ServerA and ServerB will take on the same name and IP address as
> ServerA? I'm mainly wondering since we have some windows authentication
> logins on our SQL Server and moving it to a different domain/machine would
> affect anything.
>
See http://support.microsoft.com/kb/246133/ on how to transfer logins from
one server to another.
If you rename the server you will need to drop it and re-add it. See
http://support.microsoft.com/kb/303774/
General information about moving databases see
http://support.microsoft.com/kb/314546
> Thanks in advance.
> J
John|||Thanks for the info. Much appreciated.
Take care.
J
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:FC96D7E6-AEC9-4CC7-8602-75B61F1F571E@.microsoft.com...
> Hi
> "J" wrote:
>
> See http://support.microsoft.com/kb/246133/ on how to transfer logins from
> one server to another.
> If you rename the server you will need to drop it and re-add it. See
> http://support.microsoft.com/kb/303774/
> General information about moving databases see
> http://support.microsoft.com/kb/314546
>
> Johnsql
2000 on ServerA to another SQL 2000 machine ServerB where we plan on
retiring ServerA and ServerB will take on the same name and IP address as
ServerA? I'm mainly wondering since we have some windows authentication
logins on our SQL Server and moving it to a different domain/machine would
affect anything.
Thanks in advance.
JHi
"J" wrote:
> Hello. Would anyone know of the most advisable method in moving our SQL
> 2000 on ServerA to another SQL 2000 machine ServerB where we plan on
> retiring ServerA and ServerB will take on the same name and IP address as
> ServerA? I'm mainly wondering since we have some windows authentication
> logins on our SQL Server and moving it to a different domain/machine would
> affect anything.
>
See http://support.microsoft.com/kb/246133/ on how to transfer logins from
one server to another.
If you rename the server you will need to drop it and re-add it. See
http://support.microsoft.com/kb/303774/
General information about moving databases see
http://support.microsoft.com/kb/314546
> Thanks in advance.
> J
John|||Thanks for the info. Much appreciated.
Take care.
J
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:FC96D7E6-AEC9-4CC7-8602-75B61F1F571E@.microsoft.com...
> Hi
> "J" wrote:
>
> See http://support.microsoft.com/kb/246133/ on how to transfer logins from
> one server to another.
> If you rename the server you will need to drop it and re-add it. See
> http://support.microsoft.com/kb/303774/
> General information about moving databases see
> http://support.microsoft.com/kb/314546
>
> Johnsql
Tuesday, March 20, 2012
restore question on sql2000
Hi
I have a 60 GB sql 2000 STD edition database backup.
I take backup on a remote machine A where I can restore it.
But I have to restore the same database on another machine B where it can
not restore it.
I have already copied the file over a very slow network and when I say
restore and select the backup file I do not see any datafiles listed. I clic
k
on "VIEW CONTENTS" and there is nothing.
What could cause this as same backup seen on the Machine A is fine but when
moved to machine B I can not "view the contents" and restore it.
All the version across all these machines are same.
Tks
MangeshHi
I found the reason. The copy command is still running on the Machine A for
12 hrs.
I did not know that copy command creates the file size as that of source
when it starts copy unlike ftp.
Thanks
Mangesh
"Mangesh Deshpande" wrote:
> Hi
> I have a 60 GB sql 2000 STD edition database backup.
> I take backup on a remote machine A where I can restore it.
> But I have to restore the same database on another machine B where it can
> not restore it.
> I have already copied the file over a very slow network and when I say
> restore and select the backup file I do not see any datafiles listed. I cl
ick
> on "VIEW CONTENTS" and there is nothing.
> What could cause this as same backup seen on the Machine A is fine but whe
n
> moved to machine B I can not "view the contents" and restore it.
> All the version across all these machines are same.
> Tks
> Mangesh|||Hi Mangesh,
You can try using Query Analyzer from ServerB to restore DB's from remote
locations. It is possible the backup gets corrupt during the copy. At leas
t
you can try listing the contents remotely; try this:
--
-- i.e. EXEC xp_cmdshell 'command' <-- remove any <ENTER> bewteen quotes (''
)
-- ServerA is the remote DB Server
-- Share the remote backup folder, in this example is ShareDriveA
-- account is a domain account with access to the shared folder
-- accountpassword (account password)
-- ACCOUNTDOMAIN is the domain where 'account' belongs to
EXEC xp_cmdshell 'net use \\ServerA\ShareDriveA accountpassword
/USER:ACCOUNTDOMAIN\account'
GO
-- to test if the account you used has access to the remote folder
EXEC xp_cmdshell 'dir \\ServerA\ShareFolderA\BackupFolder'
GO
-- to list the backup contents
RESTORE FILELISTONLY
FROM DISK = '\\ServerA\ShareFolder\BackupFolder\Back
upFile.BAK'
-- to finally restore the backup
RESTORE DATABASE DatabaseName
FROM DISK = '\\ServerA\ShareFolder\BackupFolder\Back
upFile.BAK'
WITH REPLACE,
MOVE 'LogicalFileName_Data' TO 'C:\SQLdata\DatabaseName.MDF',
MOVE 'LogicalFileName_Log' TO 'C:\SQLdata\DatabaseName.LDF'
--
"Mangesh Deshpande" wrote:
> Hi
> I have a 60 GB sql 2000 STD edition database backup.
> I take backup on a remote machine A where I can restore it.
> But I have to restore the same database on another machine B where it can
> not restore it.
> I have already copied the file over a very slow network and when I say
> restore and select the backup file I do not see any datafiles listed. I cl
ick
> on "VIEW CONTENTS" and there is nothing.
> What could cause this as same backup seen on the Machine A is fine but whe
n
> moved to machine B I can not "view the contents" and restore it.
> All the version across all these machines are same.
> Tks
> Mangesh
I have a 60 GB sql 2000 STD edition database backup.
I take backup on a remote machine A where I can restore it.
But I have to restore the same database on another machine B where it can
not restore it.
I have already copied the file over a very slow network and when I say
restore and select the backup file I do not see any datafiles listed. I clic
k
on "VIEW CONTENTS" and there is nothing.
What could cause this as same backup seen on the Machine A is fine but when
moved to machine B I can not "view the contents" and restore it.
All the version across all these machines are same.
Tks
MangeshHi
I found the reason. The copy command is still running on the Machine A for
12 hrs.
I did not know that copy command creates the file size as that of source
when it starts copy unlike ftp.
Thanks
Mangesh
"Mangesh Deshpande" wrote:
> Hi
> I have a 60 GB sql 2000 STD edition database backup.
> I take backup on a remote machine A where I can restore it.
> But I have to restore the same database on another machine B where it can
> not restore it.
> I have already copied the file over a very slow network and when I say
> restore and select the backup file I do not see any datafiles listed. I cl
ick
> on "VIEW CONTENTS" and there is nothing.
> What could cause this as same backup seen on the Machine A is fine but whe
n
> moved to machine B I can not "view the contents" and restore it.
> All the version across all these machines are same.
> Tks
> Mangesh|||Hi Mangesh,
You can try using Query Analyzer from ServerB to restore DB's from remote
locations. It is possible the backup gets corrupt during the copy. At leas
t
you can try listing the contents remotely; try this:
--
-- i.e. EXEC xp_cmdshell 'command' <-- remove any <ENTER> bewteen quotes (''
)
-- ServerA is the remote DB Server
-- Share the remote backup folder, in this example is ShareDriveA
-- account is a domain account with access to the shared folder
-- accountpassword (account password)
-- ACCOUNTDOMAIN is the domain where 'account' belongs to
EXEC xp_cmdshell 'net use \\ServerA\ShareDriveA accountpassword
/USER:ACCOUNTDOMAIN\account'
GO
-- to test if the account you used has access to the remote folder
EXEC xp_cmdshell 'dir \\ServerA\ShareFolderA\BackupFolder'
GO
-- to list the backup contents
RESTORE FILELISTONLY
FROM DISK = '\\ServerA\ShareFolder\BackupFolder\Back
upFile.BAK'
-- to finally restore the backup
RESTORE DATABASE DatabaseName
FROM DISK = '\\ServerA\ShareFolder\BackupFolder\Back
upFile.BAK'
WITH REPLACE,
MOVE 'LogicalFileName_Data' TO 'C:\SQLdata\DatabaseName.MDF',
MOVE 'LogicalFileName_Log' TO 'C:\SQLdata\DatabaseName.LDF'
--
"Mangesh Deshpande" wrote:
> Hi
> I have a 60 GB sql 2000 STD edition database backup.
> I take backup on a remote machine A where I can restore it.
> But I have to restore the same database on another machine B where it can
> not restore it.
> I have already copied the file over a very slow network and when I say
> restore and select the backup file I do not see any datafiles listed. I cl
ick
> on "VIEW CONTENTS" and there is nothing.
> What could cause this as same backup seen on the Machine A is fine but whe
n
> moved to machine B I can not "view the contents" and restore it.
> All the version across all these machines are same.
> Tks
> Mangesh
restore question on sql2000
Hi
I have a 60 GB sql 2000 STD edition database backup.
I take backup on a remote machine A where I can restore it.
But I have to restore the same database on another machine B where it can
not restore it.
I have already copied the file over a very slow network and when I say
restore and select the backup file I do not see any datafiles listed. I click
on "VIEW CONTENTS" and there is nothing.
What could cause this as same backup seen on the Machine A is fine but when
moved to machine B I can not "view the contents" and restore it.
All the version across all these machines are same.
Tks
Mangesh
Hi
I found the reason. The copy command is still running on the Machine A for
12 hrs.
I did not know that copy command creates the file size as that of source
when it starts copy unlike ftp.
Thanks
Mangesh
"Mangesh Deshpande" wrote:
> Hi
> I have a 60 GB sql 2000 STD edition database backup.
> I take backup on a remote machine A where I can restore it.
> But I have to restore the same database on another machine B where it can
> not restore it.
> I have already copied the file over a very slow network and when I say
> restore and select the backup file I do not see any datafiles listed. I click
> on "VIEW CONTENTS" and there is nothing.
> What could cause this as same backup seen on the Machine A is fine but when
> moved to machine B I can not "view the contents" and restore it.
> All the version across all these machines are same.
> Tks
> Mangesh
|||Hi Mangesh,
You can try using Query Analyzer from ServerB to restore DB's from remote
locations. It is possible the backup gets corrupt during the copy. At least
you can try listing the contents remotely; try this:
-- i.e. EXEC xp_cmdshell 'command' <-- remove any <ENTER> bewteen quotes ('')
-- ServerA is the remote DB Server
-- Share the remote backup folder, in this example is ShareDriveA
-- account is a domain account with access to the shared folder
-- accountpassword (account password)
-- ACCOUNTDOMAIN is the domain where 'account' belongs to
EXEC xp_cmdshell 'net use \\ServerA\ShareDriveA accountpassword
/USER:ACCOUNTDOMAIN\account'
GO
-- to test if the account you used has access to the remote folder
EXEC xp_cmdshell 'dir \\ServerA\ShareFolderA\BackupFolder'
GO
-- to list the backup contents
RESTORE FILELISTONLY
FROM DISK = '\\ServerA\ShareFolder\BackupFolder\BackupFile.BAK '
-- to finally restore the backup
RESTORE DATABASE DatabaseName
FROM DISK = '\\ServerA\ShareFolder\BackupFolder\BackupFile.BAK '
WITH REPLACE,
MOVE 'LogicalFileName_Data' TO 'C:\SQLdata\DatabaseName.MDF',
MOVE 'LogicalFileName_Log' TO 'C:\SQLdata\DatabaseName.LDF'
"Mangesh Deshpande" wrote:
> Hi
> I have a 60 GB sql 2000 STD edition database backup.
> I take backup on a remote machine A where I can restore it.
> But I have to restore the same database on another machine B where it can
> not restore it.
> I have already copied the file over a very slow network and when I say
> restore and select the backup file I do not see any datafiles listed. I click
> on "VIEW CONTENTS" and there is nothing.
> What could cause this as same backup seen on the Machine A is fine but when
> moved to machine B I can not "view the contents" and restore it.
> All the version across all these machines are same.
> Tks
> Mangesh
I have a 60 GB sql 2000 STD edition database backup.
I take backup on a remote machine A where I can restore it.
But I have to restore the same database on another machine B where it can
not restore it.
I have already copied the file over a very slow network and when I say
restore and select the backup file I do not see any datafiles listed. I click
on "VIEW CONTENTS" and there is nothing.
What could cause this as same backup seen on the Machine A is fine but when
moved to machine B I can not "view the contents" and restore it.
All the version across all these machines are same.
Tks
Mangesh
Hi
I found the reason. The copy command is still running on the Machine A for
12 hrs.
I did not know that copy command creates the file size as that of source
when it starts copy unlike ftp.
Thanks
Mangesh
"Mangesh Deshpande" wrote:
> Hi
> I have a 60 GB sql 2000 STD edition database backup.
> I take backup on a remote machine A where I can restore it.
> But I have to restore the same database on another machine B where it can
> not restore it.
> I have already copied the file over a very slow network and when I say
> restore and select the backup file I do not see any datafiles listed. I click
> on "VIEW CONTENTS" and there is nothing.
> What could cause this as same backup seen on the Machine A is fine but when
> moved to machine B I can not "view the contents" and restore it.
> All the version across all these machines are same.
> Tks
> Mangesh
|||Hi Mangesh,
You can try using Query Analyzer from ServerB to restore DB's from remote
locations. It is possible the backup gets corrupt during the copy. At least
you can try listing the contents remotely; try this:
-- i.e. EXEC xp_cmdshell 'command' <-- remove any <ENTER> bewteen quotes ('')
-- ServerA is the remote DB Server
-- Share the remote backup folder, in this example is ShareDriveA
-- account is a domain account with access to the shared folder
-- accountpassword (account password)
-- ACCOUNTDOMAIN is the domain where 'account' belongs to
EXEC xp_cmdshell 'net use \\ServerA\ShareDriveA accountpassword
/USER:ACCOUNTDOMAIN\account'
GO
-- to test if the account you used has access to the remote folder
EXEC xp_cmdshell 'dir \\ServerA\ShareFolderA\BackupFolder'
GO
-- to list the backup contents
RESTORE FILELISTONLY
FROM DISK = '\\ServerA\ShareFolder\BackupFolder\BackupFile.BAK '
-- to finally restore the backup
RESTORE DATABASE DatabaseName
FROM DISK = '\\ServerA\ShareFolder\BackupFolder\BackupFile.BAK '
WITH REPLACE,
MOVE 'LogicalFileName_Data' TO 'C:\SQLdata\DatabaseName.MDF',
MOVE 'LogicalFileName_Log' TO 'C:\SQLdata\DatabaseName.LDF'
"Mangesh Deshpande" wrote:
> Hi
> I have a 60 GB sql 2000 STD edition database backup.
> I take backup on a remote machine A where I can restore it.
> But I have to restore the same database on another machine B where it can
> not restore it.
> I have already copied the file over a very slow network and when I say
> restore and select the backup file I do not see any datafiles listed. I click
> on "VIEW CONTENTS" and there is nothing.
> What could cause this as same backup seen on the Machine A is fine but when
> moved to machine B I can not "view the contents" and restore it.
> All the version across all these machines are same.
> Tks
> Mangesh
restore question on sql2000
Hi
I have a 60 GB sql 2000 STD edition database backup.
I take backup on a remote machine A where I can restore it.
But I have to restore the same database on another machine B where it can
not restore it.
I have already copied the file over a very slow network and when I say
restore and select the backup file I do not see any datafiles listed. I click
on "VIEW CONTENTS" and there is nothing.
What could cause this as same backup seen on the Machine A is fine but when
moved to machine B I can not "view the contents" and restore it.
All the version across all these machines are same.
Tks
MangeshHi
I found the reason. The copy command is still running on the Machine A for
12 hrs.
I did not know that copy command creates the file size as that of source
when it starts copy unlike ftp.
Thanks
Mangesh
"Mangesh Deshpande" wrote:
> Hi
> I have a 60 GB sql 2000 STD edition database backup.
> I take backup on a remote machine A where I can restore it.
> But I have to restore the same database on another machine B where it can
> not restore it.
> I have already copied the file over a very slow network and when I say
> restore and select the backup file I do not see any datafiles listed. I click
> on "VIEW CONTENTS" and there is nothing.
> What could cause this as same backup seen on the Machine A is fine but when
> moved to machine B I can not "view the contents" and restore it.
> All the version across all these machines are same.
> Tks
> Mangesh|||Hi Mangesh,
You can try using Query Analyzer from ServerB to restore DB's from remote
locations. It is possible the backup gets corrupt during the copy. At least
you can try listing the contents remotely; try this:
--
-- i.e. EXEC xp_cmdshell 'command' <-- remove any <ENTER> bewteen quotes ('')
-- ServerA is the remote DB Server
-- Share the remote backup folder, in this example is ShareDriveA
-- account is a domain account with access to the shared folder
-- accountpassword (account password)
-- ACCOUNTDOMAIN is the domain where 'account' belongs to
EXEC xp_cmdshell 'net use \\ServerA\ShareDriveA accountpassword
/USER:ACCOUNTDOMAIN\account'
GO
-- to test if the account you used has access to the remote folder
EXEC xp_cmdshell 'dir \\ServerA\ShareFolderA\BackupFolder'
GO
-- to list the backup contents
RESTORE FILELISTONLY
FROM DISK = '\\ServerA\ShareFolder\BackupFolder\BackupFile.BAK'
-- to finally restore the backup
RESTORE DATABASE DatabaseName
FROM DISK = '\\ServerA\ShareFolder\BackupFolder\BackupFile.BAK'
WITH REPLACE,
MOVE 'LogicalFileName_Data' TO 'C:\SQLdata\DatabaseName.MDF',
MOVE 'LogicalFileName_Log' TO 'C:\SQLdata\DatabaseName.LDF'
--
"Mangesh Deshpande" wrote:
> Hi
> I have a 60 GB sql 2000 STD edition database backup.
> I take backup on a remote machine A where I can restore it.
> But I have to restore the same database on another machine B where it can
> not restore it.
> I have already copied the file over a very slow network and when I say
> restore and select the backup file I do not see any datafiles listed. I click
> on "VIEW CONTENTS" and there is nothing.
> What could cause this as same backup seen on the Machine A is fine but when
> moved to machine B I can not "view the contents" and restore it.
> All the version across all these machines are same.
> Tks
> Mangesh
I have a 60 GB sql 2000 STD edition database backup.
I take backup on a remote machine A where I can restore it.
But I have to restore the same database on another machine B where it can
not restore it.
I have already copied the file over a very slow network and when I say
restore and select the backup file I do not see any datafiles listed. I click
on "VIEW CONTENTS" and there is nothing.
What could cause this as same backup seen on the Machine A is fine but when
moved to machine B I can not "view the contents" and restore it.
All the version across all these machines are same.
Tks
MangeshHi
I found the reason. The copy command is still running on the Machine A for
12 hrs.
I did not know that copy command creates the file size as that of source
when it starts copy unlike ftp.
Thanks
Mangesh
"Mangesh Deshpande" wrote:
> Hi
> I have a 60 GB sql 2000 STD edition database backup.
> I take backup on a remote machine A where I can restore it.
> But I have to restore the same database on another machine B where it can
> not restore it.
> I have already copied the file over a very slow network and when I say
> restore and select the backup file I do not see any datafiles listed. I click
> on "VIEW CONTENTS" and there is nothing.
> What could cause this as same backup seen on the Machine A is fine but when
> moved to machine B I can not "view the contents" and restore it.
> All the version across all these machines are same.
> Tks
> Mangesh|||Hi Mangesh,
You can try using Query Analyzer from ServerB to restore DB's from remote
locations. It is possible the backup gets corrupt during the copy. At least
you can try listing the contents remotely; try this:
--
-- i.e. EXEC xp_cmdshell 'command' <-- remove any <ENTER> bewteen quotes ('')
-- ServerA is the remote DB Server
-- Share the remote backup folder, in this example is ShareDriveA
-- account is a domain account with access to the shared folder
-- accountpassword (account password)
-- ACCOUNTDOMAIN is the domain where 'account' belongs to
EXEC xp_cmdshell 'net use \\ServerA\ShareDriveA accountpassword
/USER:ACCOUNTDOMAIN\account'
GO
-- to test if the account you used has access to the remote folder
EXEC xp_cmdshell 'dir \\ServerA\ShareFolderA\BackupFolder'
GO
-- to list the backup contents
RESTORE FILELISTONLY
FROM DISK = '\\ServerA\ShareFolder\BackupFolder\BackupFile.BAK'
-- to finally restore the backup
RESTORE DATABASE DatabaseName
FROM DISK = '\\ServerA\ShareFolder\BackupFolder\BackupFile.BAK'
WITH REPLACE,
MOVE 'LogicalFileName_Data' TO 'C:\SQLdata\DatabaseName.MDF',
MOVE 'LogicalFileName_Log' TO 'C:\SQLdata\DatabaseName.LDF'
--
"Mangesh Deshpande" wrote:
> Hi
> I have a 60 GB sql 2000 STD edition database backup.
> I take backup on a remote machine A where I can restore it.
> But I have to restore the same database on another machine B where it can
> not restore it.
> I have already copied the file over a very slow network and when I say
> restore and select the backup file I do not see any datafiles listed. I click
> on "VIEW CONTENTS" and there is nothing.
> What could cause this as same backup seen on the Machine A is fine but when
> moved to machine B I can not "view the contents" and restore it.
> All the version across all these machines are same.
> Tks
> Mangesh
restore question
Hi
I am taking a backup of SQLSERVER on remote machine. I need to restore the
database on a daily basis on the remote machine.
I take backup of transaction log using maintenance plan every 30 mins.
It generates 48 transaciton log per day.
How can write a script to restore the database applying those 48 logs.
I can create linked server to production but what table keeps the backup log
information that I can use to build this.
Thanks
Mangesh
I keep my own table to track which log files I've applied
I store the table in a DB named "Admin"
then I select the logfiles on the file system that have not yet been applied
sorted in datetime order for example
then I apply them one at a time.
hope this makes sense.
I can dig up the scripts if you really need (But it will cost you some
Sushi)
Greg Jackson
PDX, Oregon
|||You can get all the DB backup history from the msdb database.
Specifically, you get the media_set_id values for the backups you wish
to restore from dbo.backupset based on DB name, DB vs LOG backups, dates
& times, etc., etc. And then you can get the physical file location for
those backups from dbo.backupmediafamily (using
dbo.backupset.media_set_id, which corresponds to
dbo.backupmediafamily.media_set_id). Something like:
select bs.backup_start_date, bs.type, bmf.physical_device_name
from msdb.dbo.backupset bs
inner join msdb.dbo.backupmediafamily bmf
on bmf.media_set_id = bs.media_set_id
where bs.database_name = N'MyDB'
order by bs.backup_start_date
Based on that kind of query it should be a piece of cake to automate a
restore procedure given some constraints around the restore (like
DBName, start datetime, finish datetime, etc.) also not forgetting to
restore a "D" backup followed by zero or more "L" backups.
HTH,
Mike.
PS. Do I get Sushi now?
pdxJaxon wrote:
> I keep my own table to track which log files I've applied
> I store the table in a DB named "Admin"
> then I select the logfiles on the file system that have not yet been applied
> sorted in datetime order for example
> then I apply them one at a time.
>
> hope this makes sense.
> I can dig up the scripts if you really need (But it will cost you some
> Sushi)
>
> Greg Jackson
> PDX, Oregon
>
C
|||Hi Mangesh,
If your objective is to have a standby database, have you thought of SQL
Server log-shipping as an option? Its pretty simple to set-up and get it
running.
Thanks
Yogish
I am taking a backup of SQLSERVER on remote machine. I need to restore the
database on a daily basis on the remote machine.
I take backup of transaction log using maintenance plan every 30 mins.
It generates 48 transaciton log per day.
How can write a script to restore the database applying those 48 logs.
I can create linked server to production but what table keeps the backup log
information that I can use to build this.
Thanks
Mangesh
I keep my own table to track which log files I've applied
I store the table in a DB named "Admin"
then I select the logfiles on the file system that have not yet been applied
sorted in datetime order for example
then I apply them one at a time.
hope this makes sense.
I can dig up the scripts if you really need (But it will cost you some
Sushi)
Greg Jackson
PDX, Oregon
|||You can get all the DB backup history from the msdb database.
Specifically, you get the media_set_id values for the backups you wish
to restore from dbo.backupset based on DB name, DB vs LOG backups, dates
& times, etc., etc. And then you can get the physical file location for
those backups from dbo.backupmediafamily (using
dbo.backupset.media_set_id, which corresponds to
dbo.backupmediafamily.media_set_id). Something like:
select bs.backup_start_date, bs.type, bmf.physical_device_name
from msdb.dbo.backupset bs
inner join msdb.dbo.backupmediafamily bmf
on bmf.media_set_id = bs.media_set_id
where bs.database_name = N'MyDB'
order by bs.backup_start_date
Based on that kind of query it should be a piece of cake to automate a
restore procedure given some constraints around the restore (like
DBName, start datetime, finish datetime, etc.) also not forgetting to
restore a "D" backup followed by zero or more "L" backups.
HTH,
Mike.
PS. Do I get Sushi now?
pdxJaxon wrote:
> I keep my own table to track which log files I've applied
> I store the table in a DB named "Admin"
> then I select the logfiles on the file system that have not yet been applied
> sorted in datetime order for example
> then I apply them one at a time.
>
> hope this makes sense.
> I can dig up the scripts if you really need (But it will cost you some
> Sushi)
>
> Greg Jackson
> PDX, Oregon
>
C
|||Hi Mangesh,
If your objective is to have a standby database, have you thought of SQL
Server log-shipping as an option? Its pretty simple to set-up and get it
running.
Thanks
Yogish
restore question
Hi
I am taking a backup of SQLSERVER on remote machine. I need to restore the
database on a daily basis on the remote machine.
I take backup of transaction log using maintenance plan every 30 mins.
It generates 48 transaciton log per day.
How can write a script to restore the database applying those 48 logs.
I can create linked server to production but what table keeps the backup log
information that I can use to build this.
Thanks
MangeshI keep my own table to track which log files I've applied
I store the table in a DB named "Admin"
then I select the logfiles on the file system that have not yet been applied
sorted in datetime order for example
then I apply them one at a time.
hope this makes sense.
I can dig up the scripts if you really need (But it will cost you some
Sushi)
Greg Jackson
PDX, Oregon|||You can get all the DB backup history from the msdb database.
Specifically, you get the media_set_id values for the backups you wish
to restore from dbo.backupset based on DB name, DB vs LOG backups, dates
& times, etc., etc. And then you can get the physical file location for
those backups from dbo.backupmediafamily (using
dbo.backupset.media_set_id, which corresponds to
dbo.backupmediafamily.media_set_id). Something like:
select bs.backup_start_date, bs.type, bmf.physical_device_name
from msdb.dbo.backupset bs
inner join msdb.dbo.backupmediafamily bmf
on bmf.media_set_id = bs.media_set_id
where bs.database_name = N'MyDB'
order by bs.backup_start_date
Based on that kind of query it should be a piece of cake to automate a
restore procedure given some constraints around the restore (like
DBName, start datetime, finish datetime, etc.) also not forgetting to
restore a "D" backup followed by zero or more "L" backups.
HTH,
Mike.
PS. Do I get Sushi now?
pdxJaxon wrote:
> I keep my own table to track which log files I've applied
> I store the table in a DB named "Admin"
> then I select the logfiles on the file system that have not yet been applied
> sorted in datetime order for example
> then I apply them one at a time.
>
> hope this makes sense.
> I can dig up the scripts if you really need (But it will cost you some
> Sushi)
>
> Greg Jackson
> PDX, Oregon
>
--
ÿþC|||Hi Mangesh,
If your objective is to have a standby database, have you thought of SQL
Server log-shipping as an option? Its pretty simple to set-up and get it
running.
--
Thanks
Yogish
I am taking a backup of SQLSERVER on remote machine. I need to restore the
database on a daily basis on the remote machine.
I take backup of transaction log using maintenance plan every 30 mins.
It generates 48 transaciton log per day.
How can write a script to restore the database applying those 48 logs.
I can create linked server to production but what table keeps the backup log
information that I can use to build this.
Thanks
MangeshI keep my own table to track which log files I've applied
I store the table in a DB named "Admin"
then I select the logfiles on the file system that have not yet been applied
sorted in datetime order for example
then I apply them one at a time.
hope this makes sense.
I can dig up the scripts if you really need (But it will cost you some
Sushi)
Greg Jackson
PDX, Oregon|||You can get all the DB backup history from the msdb database.
Specifically, you get the media_set_id values for the backups you wish
to restore from dbo.backupset based on DB name, DB vs LOG backups, dates
& times, etc., etc. And then you can get the physical file location for
those backups from dbo.backupmediafamily (using
dbo.backupset.media_set_id, which corresponds to
dbo.backupmediafamily.media_set_id). Something like:
select bs.backup_start_date, bs.type, bmf.physical_device_name
from msdb.dbo.backupset bs
inner join msdb.dbo.backupmediafamily bmf
on bmf.media_set_id = bs.media_set_id
where bs.database_name = N'MyDB'
order by bs.backup_start_date
Based on that kind of query it should be a piece of cake to automate a
restore procedure given some constraints around the restore (like
DBName, start datetime, finish datetime, etc.) also not forgetting to
restore a "D" backup followed by zero or more "L" backups.
HTH,
Mike.
PS. Do I get Sushi now?
pdxJaxon wrote:
> I keep my own table to track which log files I've applied
> I store the table in a DB named "Admin"
> then I select the logfiles on the file system that have not yet been applied
> sorted in datetime order for example
> then I apply them one at a time.
>
> hope this makes sense.
> I can dig up the scripts if you really need (But it will cost you some
> Sushi)
>
> Greg Jackson
> PDX, Oregon
>
--
ÿþC|||Hi Mangesh,
If your objective is to have a standby database, have you thought of SQL
Server log-shipping as an option? Its pretty simple to set-up and get it
running.
--
Thanks
Yogish
restore question
Hi
I am taking a backup of SQLSERVER on remote machine. I need to restore the
database on a daily basis on the remote machine.
I take backup of transaction log using maintenance plan every 30 mins.
It generates 48 transaciton log per day.
How can write a script to restore the database applying those 48 logs.
I can create linked server to production but what table keeps the backup log
information that I can use to build this.
Thanks
MangeshI keep my own table to track which log files I've applied
I store the table in a DB named "Admin"
then I select the logfiles on the file system that have not yet been applied
sorted in datetime order for example
then I apply them one at a time.
hope this makes sense.
I can dig up the scripts if you really need (But it will cost you some
Sushi)
Greg Jackson
PDX, Oregon|||You can get all the DB backup history from the msdb database.
Specifically, you get the media_set_id values for the backups you wish
to restore from dbo.backupset based on DB name, DB vs LOG backups, dates
& times, etc., etc. And then you can get the physical file location for
those backups from dbo.backupmediafamily (using
dbo.backupset.media_set_id, which corresponds to
dbo.backupmediafamily.media_set_id). Something like:
select bs.backup_start_date, bs.type, bmf.physical_device_name
from msdb.dbo.backupset bs
inner join msdb.dbo.backupmediafamily bmf
on bmf.media_set_id = bs.media_set_id
where bs.database_name = N'MyDB'
order by bs.backup_start_date
Based on that kind of query it should be a piece of cake to automate a
restore procedure given some constraints around the restore (like
DBName, start datetime, finish datetime, etc.) also not forgetting to
restore a "D" backup followed by zero or more "L" backups.
HTH,
Mike.
PS. Do I get Sushi now?
pdxJaxon wrote:
> I keep my own table to track which log files I've applied
> I store the table in a DB named "Admin"
> then I select the logfiles on the file system that have not yet been appli
ed
> sorted in datetime order for example
> then I apply them one at a time.
>
> hope this makes sense.
> I can dig up the scripts if you really need (But it will cost you some
> Sushi)
>
> Greg Jackson
> PDX, Oregon
>
C|||Hi Mangesh,
If your objective is to have a standby database, have you thought of SQL
Server log-shipping as an option? Its pretty simple to set-up and get it
running.
Thanks
Yogish
I am taking a backup of SQLSERVER on remote machine. I need to restore the
database on a daily basis on the remote machine.
I take backup of transaction log using maintenance plan every 30 mins.
It generates 48 transaciton log per day.
How can write a script to restore the database applying those 48 logs.
I can create linked server to production but what table keeps the backup log
information that I can use to build this.
Thanks
MangeshI keep my own table to track which log files I've applied
I store the table in a DB named "Admin"
then I select the logfiles on the file system that have not yet been applied
sorted in datetime order for example
then I apply them one at a time.
hope this makes sense.
I can dig up the scripts if you really need (But it will cost you some
Sushi)
Greg Jackson
PDX, Oregon|||You can get all the DB backup history from the msdb database.
Specifically, you get the media_set_id values for the backups you wish
to restore from dbo.backupset based on DB name, DB vs LOG backups, dates
& times, etc., etc. And then you can get the physical file location for
those backups from dbo.backupmediafamily (using
dbo.backupset.media_set_id, which corresponds to
dbo.backupmediafamily.media_set_id). Something like:
select bs.backup_start_date, bs.type, bmf.physical_device_name
from msdb.dbo.backupset bs
inner join msdb.dbo.backupmediafamily bmf
on bmf.media_set_id = bs.media_set_id
where bs.database_name = N'MyDB'
order by bs.backup_start_date
Based on that kind of query it should be a piece of cake to automate a
restore procedure given some constraints around the restore (like
DBName, start datetime, finish datetime, etc.) also not forgetting to
restore a "D" backup followed by zero or more "L" backups.
HTH,
Mike.
PS. Do I get Sushi now?
pdxJaxon wrote:
> I keep my own table to track which log files I've applied
> I store the table in a DB named "Admin"
> then I select the logfiles on the file system that have not yet been appli
ed
> sorted in datetime order for example
> then I apply them one at a time.
>
> hope this makes sense.
> I can dig up the scripts if you really need (But it will cost you some
> Sushi)
>
> Greg Jackson
> PDX, Oregon
>
C|||Hi Mangesh,
If your objective is to have a standby database, have you thought of SQL
Server log-shipping as an option? Its pretty simple to set-up and get it
running.
Thanks
Yogish
Monday, March 12, 2012
restore problem about sql server
i reinstall the sql server on the machine, and use attach file method
to get the database back, and it works well on the server, which means
i can get the data using Query analyser, but when i use the web
application to access the database, it always come out with error
message, it seems that the connection to the database can not be
established, but it used to be ok before i reinstalled the sql server.
do i need to do any configuration after attaching the data files and
log files(.mdf and .ldf).
to get the database back, and it works well on the server, which means
i can get the data using Query analyser, but when i use the web
application to access the database, it always come out with error
message, it seems that the connection to the database can not be
established, but it used to be ok before i reinstalled the sql server.
do i need to do any configuration after attaching the data files and
log files(.mdf and .ldf).
i think the source code(i mean the database connection code) for the
web application should be fine caze i didnt change it before after.
caze i didnt create instance of database and just use default, so the
connection string is defined below:
thisConnection = new SqlConnection(@."Data Source=pdsmfg014;Initial
Catalog=epcsii;User ID=epcs2;Password=******")
the server name is pdsmfg014
the database name is epcsii
oh, the code is designed using C#Dee (luye_qq@.hotmail.com) writes:
> i reinstall the sql server on the machine, and use attach file method
> to get the database back, and it works well on the server, which means
> i can get the data using Query analyser, but when i use the web
> application to access the database, it always come out with error
> message, it seems that the connection to the database can not be
> established, but it used to be ok before i reinstalled the sql server.
> do i need to do any configuration after attaching the data files and
> log files(.mdf and .ldf).
> i think the source code(i mean the database connection code) for the
> web application should be fine caze i didnt change it before after.
> caze i didnt create instance of database and just use default, so the
> connection string is defined below:
> thisConnection = new SqlConnection(@."Data Source=pdsmfg014;Initial
> Catalog=epcsii;User ID=epcs2;Password=******")
> the server name is pdsmfg014
> the database name is epcsii
So is this login epcs2 present on the reinstalled server? In such
case it could be that when you reinstalled the server the mapping
between logins and database users were lost. Run sp_helpuser in the
database and see if the output makes sense.
If not the procedure sp_changes_users_login can help you. Please check
Books Online for details.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||thx, erland,
I think the databse is working properly right now.
it must be some OS environment problems that prevent the application
accessing the database.
caze i migrate the application to my laptop and also install the SQL
server on my laptop to access the database, it works. it just means,
the laptop is my application server ,and the original server is just
the database server.
thus, there is sth wrong with my IIS setting probably, but I dont know
how to fig it out.
anyone can help?|||Hi,
You did not mention what kind of error you are getting.
If you are getting access denied error then make sure your Sql instance
authentication is eiter mixed mode or in SQl server authentication mode
and check the user has proper permission on that server, the easiest
way to check is open query analyzer from your laptop and give the same
server name(type id down), userid and password.
besides this make sure both database server and your laptop are in the
same domain and also you can try switching off the windows xp fire
wall.
bye
ssk
Dee wrote:
> thx, erland,
> I think the databse is working properly right now.
> it must be some OS environment problems that prevent the application
> accessing the database.
> caze i migrate the application to my laptop and also install the SQL
> server on my laptop to access the database, it works. it just means,
> the laptop is my application server ,and the original server is just
> the database server.
> thus, there is sth wrong with my IIS setting probably, but I dont know
> how to fig it out.
> anyone can help?|||Dee (luye_qq@.hotmail.com) writes:
> I think the databse is working properly right now.
> it must be some OS environment problems that prevent the application
> accessing the database.
> caze i migrate the application to my laptop and also install the SQL
> server on my laptop to access the database, it works. it just means,
> the laptop is my application server ,and the original server is just
> the database server.
> thus, there is sth wrong with my IIS setting probably, but I dont know
> how to fig it out.
> anyone can help?
As a start, please post the exact error message you are getting.
Did you perform the check with sp_helpuser, that I suggested?
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp
Subscribe to:
Posts (Atom)