I am trying to install on SQL Server 2000 on Windows server 2003, web
edition. When I click on autorun, then choose server tools and components and
choose Install Server, nothing happens.
I was wondering if it possible to install SQL Server 2000 on Windows Server
2003 web edition. Is this a compatibility issue'
Thank you.
VamsheeWindows Server 2003 Web Server Edition will not allow you to install SQL
Server 2000. It is not a licensed configuration.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Vamshee" <Vamshee@.discussions.microsoft.com> wrote in message
news:56A57D60-720F-4512-AA27-53045E73DD7C@.microsoft.com...
> I am trying to install on SQL Server 2000 on Windows server 2003, web
> edition. When I click on autorun, then choose server tools and components
and
> choose Install Server, nothing happens.
> I was wondering if it possible to install SQL Server 2000 on Windows
Server
> 2003 web edition. Is this a compatibility issue'
> Thank you.
> Vamshee|||Hi,
Organizations cannot use Windows Server 2003, Web Edition, to deploy
Microsoft SQL Server.
See the below link (Limitations paragraph):-
http://www.microsoft.com/windowsserver2003/evaluation/overview/web.mspx
Thanks
Hari
SQL Server MVP
"Geoff N. Hiten" wrote:
> Windows Server 2003 Web Server Edition will not allow you to install SQL
> Server 2000. It is not a licensed configuration.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Vamshee" <Vamshee@.discussions.microsoft.com> wrote in message
> news:56A57D60-720F-4512-AA27-53045E73DD7C@.microsoft.com...
> > I am trying to install on SQL Server 2000 on Windows server 2003, web
> > edition. When I click on autorun, then choose server tools and components
> and
> > choose Install Server, nothing happens.
> >
> > I was wondering if it possible to install SQL Server 2000 on Windows
> Server
> > 2003 web edition. Is this a compatibility issue'
> >
> > Thank you.
> > Vamshee
>
>|||Thanks for the information.
"Hari Prasad" wrote:
> Hi,
> Organizations cannot use Windows Server 2003, Web Edition, to deploy
> Microsoft SQL Server.
> See the below link (Limitations paragraph):-
> http://www.microsoft.com/windowsserver2003/evaluation/overview/web.mspx
> Thanks
> Hari
> SQL Server MVP
>
> "Geoff N. Hiten" wrote:
> > Windows Server 2003 Web Server Edition will not allow you to install SQL
> > Server 2000. It is not a licensed configuration.
> >
> > --
> > Geoff N. Hiten
> > Microsoft SQL Server MVP
> > Senior Database Administrator
> > Careerbuilder.com
> >
> > I support the Professional Association for SQL Server
> > www.sqlpass.org
> >
> > "Vamshee" <Vamshee@.discussions.microsoft.com> wrote in message
> > news:56A57D60-720F-4512-AA27-53045E73DD7C@.microsoft.com...
> > > I am trying to install on SQL Server 2000 on Windows server 2003, web
> > > edition. When I click on autorun, then choose server tools and components
> > and
> > > choose Install Server, nothing happens.
> > >
> > > I was wondering if it possible to install SQL Server 2000 on Windows
> > Server
> > > 2003 web edition. Is this a compatibility issue'
> > >
> > > Thank you.
> > > Vamshee
> >
> >
> >sql
Showing posts with label edition. Show all posts
Showing posts with label edition. Show all posts
Wednesday, March 21, 2012
Tuesday, March 20, 2012
question on recovery sql server 2000
Hi
I am using SQL 2000 std edition and hence using custom scripts to
restore the DB using standby file. I am backing up T-LOGs every 30 mins on
production and copying them on a network location which is accessible to
standby machine.
I run a job on standby machine which applies the transaction logs every 30
mins by checking in backmediaset & backupmediafamily tables of Production. DB
is running in read only and is working.
Question : In case my Production machine goes down and does not come up how
can I start the Standby "with data loss" if it has already appiled the last
T-logs generated on production.
Since Produciton (primary) is down I can not backup the last T-log.
Thanks
Mangesh
From BOL
This example sets up the MyNwind database on a standby server. The database
can be used in read-only mode between restore operations.
-- Restore the initial database backup on the standby server.
USE master
GO
RESTORE DATABASE MyNwind
FROM MyNwind_1
WITH STANDBY = 'c:\undo.ldf'
GO
-- Apply the first transaction log backup.
RESTORE LOG MyNwind
FROM MyNwind_log1
WITH STANDBY = 'c:\undo.ldf'
GO
-- Apply the next transaction log backup.
RESTORE LOG MyNwind
FROM MyNwind_log2
WITH STANDBY = 'c:\undo.ldf'
GO
-- Repeat for each transaction log backup created on the
-- primary server.
-- Time elapses.. .. ..
-- The primary server has failed. Back up the
-- active transaction log on the primary server.
BACKUP LOG MyNwind
TO MyNwind_log3
WITH NO_TRUNCATE
GO
-- Apply the final (active) transaction log backup
-- to the standby server. All preceding transaction
-- log backups must have been already applied.
RESTORE LOG MyNwind
FROM MyNwind_log3
WITH STANDBY = 'c:\undo.ldf'
GO
-- Recover the database on the standby server,
-- making it available for normal operations.
RESTORE DATABASE MyNwind
WITH RECOVERY
GO
"Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in
message news:72D84926-67E3-4A3F-A011-E5F5A6ACA8CC@.microsoft.com...
> Hi
> I am using SQL 2000 std edition and hence using custom scripts to
> restore the DB using standby file. I am backing up T-LOGs every 30 mins on
> production and copying them on a network location which is accessible to
> standby machine.
> I run a job on standby machine which applies the transaction logs every 30
> mins by checking in backmediaset & backupmediafamily tables of Production.
DB
> is running in read only and is working.
> Question : In case my Production machine goes down and does not come up
how
> can I start the Standby "with data loss" if it has already appiled the
last
> T-logs generated on production.
> Since Produciton (primary) is down I can not backup the last T-log.
> Thanks
> Mangesh
>
|||So you are continuously doing RESTORE WITH STANDBY? And you now wand to make the database fully
accessible? If so:
RESTORE DATABASE dbname WITH RECOVERY
No actual restore is performed, only the recovery work to get it out of standby mode.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in message
news:72D84926-67E3-4A3F-A011-E5F5A6ACA8CC@.microsoft.com...
> Hi
> I am using SQL 2000 std edition and hence using custom scripts to
> restore the DB using standby file. I am backing up T-LOGs every 30 mins on
> production and copying them on a network location which is accessible to
> standby machine.
> I run a job on standby machine which applies the transaction logs every 30
> mins by checking in backmediaset & backupmediafamily tables of Production. DB
> is running in read only and is working.
> Question : In case my Production machine goes down and does not come up how
> can I start the Standby "with data loss" if it has already appiled the last
> T-logs generated on production.
> Since Produciton (primary) is down I can not backup the last T-log.
> Thanks
> Mangesh
>
|||Yes. I am doing a continuous restoration of my standby database using standby
file.
Thanks for help.
"Tibor Karaszi" wrote:
> So you are continuously doing RESTORE WITH STANDBY? And you now wand to make the database fully
> accessible? If so:
> RESTORE DATABASE dbname WITH RECOVERY
> No actual restore is performed, only the recovery work to get it out of standby mode.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in message
> news:72D84926-67E3-4A3F-A011-E5F5A6ACA8CC@.microsoft.com...
>
>
I am using SQL 2000 std edition and hence using custom scripts to
restore the DB using standby file. I am backing up T-LOGs every 30 mins on
production and copying them on a network location which is accessible to
standby machine.
I run a job on standby machine which applies the transaction logs every 30
mins by checking in backmediaset & backupmediafamily tables of Production. DB
is running in read only and is working.
Question : In case my Production machine goes down and does not come up how
can I start the Standby "with data loss" if it has already appiled the last
T-logs generated on production.
Since Produciton (primary) is down I can not backup the last T-log.
Thanks
Mangesh
From BOL
This example sets up the MyNwind database on a standby server. The database
can be used in read-only mode between restore operations.
-- Restore the initial database backup on the standby server.
USE master
GO
RESTORE DATABASE MyNwind
FROM MyNwind_1
WITH STANDBY = 'c:\undo.ldf'
GO
-- Apply the first transaction log backup.
RESTORE LOG MyNwind
FROM MyNwind_log1
WITH STANDBY = 'c:\undo.ldf'
GO
-- Apply the next transaction log backup.
RESTORE LOG MyNwind
FROM MyNwind_log2
WITH STANDBY = 'c:\undo.ldf'
GO
-- Repeat for each transaction log backup created on the
-- primary server.
-- Time elapses.. .. ..
-- The primary server has failed. Back up the
-- active transaction log on the primary server.
BACKUP LOG MyNwind
TO MyNwind_log3
WITH NO_TRUNCATE
GO
-- Apply the final (active) transaction log backup
-- to the standby server. All preceding transaction
-- log backups must have been already applied.
RESTORE LOG MyNwind
FROM MyNwind_log3
WITH STANDBY = 'c:\undo.ldf'
GO
-- Recover the database on the standby server,
-- making it available for normal operations.
RESTORE DATABASE MyNwind
WITH RECOVERY
GO
"Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in
message news:72D84926-67E3-4A3F-A011-E5F5A6ACA8CC@.microsoft.com...
> Hi
> I am using SQL 2000 std edition and hence using custom scripts to
> restore the DB using standby file. I am backing up T-LOGs every 30 mins on
> production and copying them on a network location which is accessible to
> standby machine.
> I run a job on standby machine which applies the transaction logs every 30
> mins by checking in backmediaset & backupmediafamily tables of Production.
DB
> is running in read only and is working.
> Question : In case my Production machine goes down and does not come up
how
> can I start the Standby "with data loss" if it has already appiled the
last
> T-logs generated on production.
> Since Produciton (primary) is down I can not backup the last T-log.
> Thanks
> Mangesh
>
|||So you are continuously doing RESTORE WITH STANDBY? And you now wand to make the database fully
accessible? If so:
RESTORE DATABASE dbname WITH RECOVERY
No actual restore is performed, only the recovery work to get it out of standby mode.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in message
news:72D84926-67E3-4A3F-A011-E5F5A6ACA8CC@.microsoft.com...
> Hi
> I am using SQL 2000 std edition and hence using custom scripts to
> restore the DB using standby file. I am backing up T-LOGs every 30 mins on
> production and copying them on a network location which is accessible to
> standby machine.
> I run a job on standby machine which applies the transaction logs every 30
> mins by checking in backmediaset & backupmediafamily tables of Production. DB
> is running in read only and is working.
> Question : In case my Production machine goes down and does not come up how
> can I start the Standby "with data loss" if it has already appiled the last
> T-logs generated on production.
> Since Produciton (primary) is down I can not backup the last T-log.
> Thanks
> Mangesh
>
|||Yes. I am doing a continuous restoration of my standby database using standby
file.
Thanks for help.
"Tibor Karaszi" wrote:
> So you are continuously doing RESTORE WITH STANDBY? And you now wand to make the database fully
> accessible? If so:
> RESTORE DATABASE dbname WITH RECOVERY
> No actual restore is performed, only the recovery work to get it out of standby mode.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in message
> news:72D84926-67E3-4A3F-A011-E5F5A6ACA8CC@.microsoft.com...
>
>
question on recovery sql server 2000
Hi
I am using SQL 2000 std edition and hence using custom scripts to
restore the DB using standby file. I am backing up T-LOGs every 30 mins on
production and copying them on a network location which is accessible to
standby machine.
I run a job on standby machine which applies the transaction logs every 30
mins by checking in backmediaset & backupmediafamily tables of Production. D
B
is running in read only and is working.
Question : In case my Production machine goes down and does not come up how
can I start the Standby "with data loss" if it has already appiled the last
T-logs generated on production.
Since Produciton (primary) is down I can not backup the last T-log.
Thanks
MangeshFrom BOL
This example sets up the MyNwind database on a standby server. The database
can be used in read-only mode between restore operations.
-- Restore the initial database backup on the standby server.
USE master
GO
RESTORE DATABASE MyNwind
FROM MyNwind_1
WITH STANDBY = 'c:\undo.ldf'
GO
-- Apply the first transaction log backup.
RESTORE LOG MyNwind
FROM MyNwind_log1
WITH STANDBY = 'c:\undo.ldf'
GO
-- Apply the next transaction log backup.
RESTORE LOG MyNwind
FROM MyNwind_log2
WITH STANDBY = 'c:\undo.ldf'
GO
-- Repeat for each transaction log backup created on the
-- primary server.
--
-- Time elapses.. .. ..
--
-- The primary server has failed. Back up the
-- active transaction log on the primary server.
BACKUP LOG MyNwind
TO MyNwind_log3
WITH NO_TRUNCATE
GO
-- Apply the final (active) transaction log backup
-- to the standby server. All preceding transaction
-- log backups must have been already applied.
RESTORE LOG MyNwind
FROM MyNwind_log3
WITH STANDBY = 'c:\undo.ldf'
GO
-- Recover the database on the standby server,
-- making it available for normal operations.
RESTORE DATABASE MyNwind
WITH RECOVERY
GO
"Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in
message news:72D84926-67E3-4A3F-A011-E5F5A6ACA8CC@.microsoft.com...
> Hi
> I am using SQL 2000 std edition and hence using custom scripts to
> restore the DB using standby file. I am backing up T-LOGs every 30 mins on
> production and copying them on a network location which is accessible to
> standby machine.
> I run a job on standby machine which applies the transaction logs every 30
> mins by checking in backmediaset & backupmediafamily tables of Production.
DB
> is running in read only and is working.
> Question : In case my Production machine goes down and does not come up
how
> can I start the Standby "with data loss" if it has already appiled the
last
> T-logs generated on production.
> Since Produciton (primary) is down I can not backup the last T-log.
> Thanks
> Mangesh
>|||So you are continuously doing RESTORE WITH STANDBY? And you now wand to make
the database fully
accessible? If so:
RESTORE DATABASE dbname WITH RECOVERY
No actual restore is performed, only the recovery work to get it out of stan
dby mode.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in me
ssage
news:72D84926-67E3-4A3F-A011-E5F5A6ACA8CC@.microsoft.com...
> Hi
> I am using SQL 2000 std edition and hence using custom scripts to
> restore the DB using standby file. I am backing up T-LOGs every 30 mins on
> production and copying them on a network location which is accessible to
> standby machine.
> I run a job on standby machine which applies the transaction logs every 30
> mins by checking in backmediaset & backupmediafamily tables of Production.
DB
> is running in read only and is working.
> Question : In case my Production machine goes down and does not come up h
ow
> can I start the Standby "with data loss" if it has already appiled the las
t
> T-logs generated on production.
> Since Produciton (primary) is down I can not backup the last T-log.
> Thanks
> Mangesh
>|||Yes. I am doing a continuous restoration of my standby database using standb
y
file.
Thanks for help.
"Tibor Karaszi" wrote:
> So you are continuously doing RESTORE WITH STANDBY? And you now wand to ma
ke the database fully
> accessible? If so:
> RESTORE DATABASE dbname WITH RECOVERY
> No actual restore is performed, only the recovery work to get it out of st
andby mode.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in
message
> news:72D84926-67E3-4A3F-A011-E5F5A6ACA8CC@.microsoft.com...
>
>
I am using SQL 2000 std edition and hence using custom scripts to
restore the DB using standby file. I am backing up T-LOGs every 30 mins on
production and copying them on a network location which is accessible to
standby machine.
I run a job on standby machine which applies the transaction logs every 30
mins by checking in backmediaset & backupmediafamily tables of Production. D
B
is running in read only and is working.
Question : In case my Production machine goes down and does not come up how
can I start the Standby "with data loss" if it has already appiled the last
T-logs generated on production.
Since Produciton (primary) is down I can not backup the last T-log.
Thanks
MangeshFrom BOL
This example sets up the MyNwind database on a standby server. The database
can be used in read-only mode between restore operations.
-- Restore the initial database backup on the standby server.
USE master
GO
RESTORE DATABASE MyNwind
FROM MyNwind_1
WITH STANDBY = 'c:\undo.ldf'
GO
-- Apply the first transaction log backup.
RESTORE LOG MyNwind
FROM MyNwind_log1
WITH STANDBY = 'c:\undo.ldf'
GO
-- Apply the next transaction log backup.
RESTORE LOG MyNwind
FROM MyNwind_log2
WITH STANDBY = 'c:\undo.ldf'
GO
-- Repeat for each transaction log backup created on the
-- primary server.
--
-- Time elapses.. .. ..
--
-- The primary server has failed. Back up the
-- active transaction log on the primary server.
BACKUP LOG MyNwind
TO MyNwind_log3
WITH NO_TRUNCATE
GO
-- Apply the final (active) transaction log backup
-- to the standby server. All preceding transaction
-- log backups must have been already applied.
RESTORE LOG MyNwind
FROM MyNwind_log3
WITH STANDBY = 'c:\undo.ldf'
GO
-- Recover the database on the standby server,
-- making it available for normal operations.
RESTORE DATABASE MyNwind
WITH RECOVERY
GO
"Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in
message news:72D84926-67E3-4A3F-A011-E5F5A6ACA8CC@.microsoft.com...
> Hi
> I am using SQL 2000 std edition and hence using custom scripts to
> restore the DB using standby file. I am backing up T-LOGs every 30 mins on
> production and copying them on a network location which is accessible to
> standby machine.
> I run a job on standby machine which applies the transaction logs every 30
> mins by checking in backmediaset & backupmediafamily tables of Production.
DB
> is running in read only and is working.
> Question : In case my Production machine goes down and does not come up
how
> can I start the Standby "with data loss" if it has already appiled the
last
> T-logs generated on production.
> Since Produciton (primary) is down I can not backup the last T-log.
> Thanks
> Mangesh
>|||So you are continuously doing RESTORE WITH STANDBY? And you now wand to make
the database fully
accessible? If so:
RESTORE DATABASE dbname WITH RECOVERY
No actual restore is performed, only the recovery work to get it out of stan
dby mode.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in me
ssage
news:72D84926-67E3-4A3F-A011-E5F5A6ACA8CC@.microsoft.com...
> Hi
> I am using SQL 2000 std edition and hence using custom scripts to
> restore the DB using standby file. I am backing up T-LOGs every 30 mins on
> production and copying them on a network location which is accessible to
> standby machine.
> I run a job on standby machine which applies the transaction logs every 30
> mins by checking in backmediaset & backupmediafamily tables of Production.
DB
> is running in read only and is working.
> Question : In case my Production machine goes down and does not come up h
ow
> can I start the Standby "with data loss" if it has already appiled the las
t
> T-logs generated on production.
> Since Produciton (primary) is down I can not backup the last T-log.
> Thanks
> Mangesh
>|||Yes. I am doing a continuous restoration of my standby database using standb
y
file.
Thanks for help.
"Tibor Karaszi" wrote:
> So you are continuously doing RESTORE WITH STANDBY? And you now wand to ma
ke the database fully
> accessible? If so:
> RESTORE DATABASE dbname WITH RECOVERY
> No actual restore is performed, only the recovery work to get it out of st
andby mode.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in
message
> news:72D84926-67E3-4A3F-A011-E5F5A6ACA8CC@.microsoft.com...
>
>
question on recovery sql server 2000
Hi
I am using SQL 2000 std edition and hence using custom scripts to
restore the DB using standby file. I am backing up T-LOGs every 30 mins on
production and copying them on a network location which is accessible to
standby machine.
I run a job on standby machine which applies the transaction logs every 30
mins by checking in backmediaset & backupmediafamily tables of Production. DB
is running in read only and is working.
Question : In case my Production machine goes down and does not come up how
can I start the Standby "with data loss" if it has already appiled the last
T-logs generated on production.
Since Produciton (primary) is down I can not backup the last T-log.
Thanks
MangeshFrom BOL
This example sets up the MyNwind database on a standby server. The database
can be used in read-only mode between restore operations.
-- Restore the initial database backup on the standby server.
USE master
GO
RESTORE DATABASE MyNwind
FROM MyNwind_1
WITH STANDBY = 'c:\undo.ldf'
GO
-- Apply the first transaction log backup.
RESTORE LOG MyNwind
FROM MyNwind_log1
WITH STANDBY = 'c:\undo.ldf'
GO
-- Apply the next transaction log backup.
RESTORE LOG MyNwind
FROM MyNwind_log2
WITH STANDBY = 'c:\undo.ldf'
GO
-- Repeat for each transaction log backup created on the
-- primary server.
--
-- Time elapses.. .. ..
--
-- The primary server has failed. Back up the
-- active transaction log on the primary server.
BACKUP LOG MyNwind
TO MyNwind_log3
WITH NO_TRUNCATE
GO
-- Apply the final (active) transaction log backup
-- to the standby server. All preceding transaction
-- log backups must have been already applied.
RESTORE LOG MyNwind
FROM MyNwind_log3
WITH STANDBY = 'c:\undo.ldf'
GO
-- Recover the database on the standby server,
-- making it available for normal operations.
RESTORE DATABASE MyNwind
WITH RECOVERY
GO
"Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in
message news:72D84926-67E3-4A3F-A011-E5F5A6ACA8CC@.microsoft.com...
> Hi
> I am using SQL 2000 std edition and hence using custom scripts to
> restore the DB using standby file. I am backing up T-LOGs every 30 mins on
> production and copying them on a network location which is accessible to
> standby machine.
> I run a job on standby machine which applies the transaction logs every 30
> mins by checking in backmediaset & backupmediafamily tables of Production.
DB
> is running in read only and is working.
> Question : In case my Production machine goes down and does not come up
how
> can I start the Standby "with data loss" if it has already appiled the
last
> T-logs generated on production.
> Since Produciton (primary) is down I can not backup the last T-log.
> Thanks
> Mangesh
>|||So you are continuously doing RESTORE WITH STANDBY? And you now wand to make the database fully
accessible? If so:
RESTORE DATABASE dbname WITH RECOVERY
No actual restore is performed, only the recovery work to get it out of standby mode.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in message
news:72D84926-67E3-4A3F-A011-E5F5A6ACA8CC@.microsoft.com...
> Hi
> I am using SQL 2000 std edition and hence using custom scripts to
> restore the DB using standby file. I am backing up T-LOGs every 30 mins on
> production and copying them on a network location which is accessible to
> standby machine.
> I run a job on standby machine which applies the transaction logs every 30
> mins by checking in backmediaset & backupmediafamily tables of Production. DB
> is running in read only and is working.
> Question : In case my Production machine goes down and does not come up how
> can I start the Standby "with data loss" if it has already appiled the last
> T-logs generated on production.
> Since Produciton (primary) is down I can not backup the last T-log.
> Thanks
> Mangesh
>|||Yes. I am doing a continuous restoration of my standby database using standby
file.
Thanks for help.
"Tibor Karaszi" wrote:
> So you are continuously doing RESTORE WITH STANDBY? And you now wand to make the database fully
> accessible? If so:
> RESTORE DATABASE dbname WITH RECOVERY
> No actual restore is performed, only the recovery work to get it out of standby mode.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in message
> news:72D84926-67E3-4A3F-A011-E5F5A6ACA8CC@.microsoft.com...
> > Hi
> >
> > I am using SQL 2000 std edition and hence using custom scripts to
> > restore the DB using standby file. I am backing up T-LOGs every 30 mins on
> > production and copying them on a network location which is accessible to
> > standby machine.
> >
> > I run a job on standby machine which applies the transaction logs every 30
> > mins by checking in backmediaset & backupmediafamily tables of Production. DB
> > is running in read only and is working.
> >
> > Question : In case my Production machine goes down and does not come up how
> > can I start the Standby "with data loss" if it has already appiled the last
> > T-logs generated on production.
> > Since Produciton (primary) is down I can not backup the last T-log.
> >
> > Thanks
> > Mangesh
> >
> >
>
>
I am using SQL 2000 std edition and hence using custom scripts to
restore the DB using standby file. I am backing up T-LOGs every 30 mins on
production and copying them on a network location which is accessible to
standby machine.
I run a job on standby machine which applies the transaction logs every 30
mins by checking in backmediaset & backupmediafamily tables of Production. DB
is running in read only and is working.
Question : In case my Production machine goes down and does not come up how
can I start the Standby "with data loss" if it has already appiled the last
T-logs generated on production.
Since Produciton (primary) is down I can not backup the last T-log.
Thanks
MangeshFrom BOL
This example sets up the MyNwind database on a standby server. The database
can be used in read-only mode between restore operations.
-- Restore the initial database backup on the standby server.
USE master
GO
RESTORE DATABASE MyNwind
FROM MyNwind_1
WITH STANDBY = 'c:\undo.ldf'
GO
-- Apply the first transaction log backup.
RESTORE LOG MyNwind
FROM MyNwind_log1
WITH STANDBY = 'c:\undo.ldf'
GO
-- Apply the next transaction log backup.
RESTORE LOG MyNwind
FROM MyNwind_log2
WITH STANDBY = 'c:\undo.ldf'
GO
-- Repeat for each transaction log backup created on the
-- primary server.
--
-- Time elapses.. .. ..
--
-- The primary server has failed. Back up the
-- active transaction log on the primary server.
BACKUP LOG MyNwind
TO MyNwind_log3
WITH NO_TRUNCATE
GO
-- Apply the final (active) transaction log backup
-- to the standby server. All preceding transaction
-- log backups must have been already applied.
RESTORE LOG MyNwind
FROM MyNwind_log3
WITH STANDBY = 'c:\undo.ldf'
GO
-- Recover the database on the standby server,
-- making it available for normal operations.
RESTORE DATABASE MyNwind
WITH RECOVERY
GO
"Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in
message news:72D84926-67E3-4A3F-A011-E5F5A6ACA8CC@.microsoft.com...
> Hi
> I am using SQL 2000 std edition and hence using custom scripts to
> restore the DB using standby file. I am backing up T-LOGs every 30 mins on
> production and copying them on a network location which is accessible to
> standby machine.
> I run a job on standby machine which applies the transaction logs every 30
> mins by checking in backmediaset & backupmediafamily tables of Production.
DB
> is running in read only and is working.
> Question : In case my Production machine goes down and does not come up
how
> can I start the Standby "with data loss" if it has already appiled the
last
> T-logs generated on production.
> Since Produciton (primary) is down I can not backup the last T-log.
> Thanks
> Mangesh
>|||So you are continuously doing RESTORE WITH STANDBY? And you now wand to make the database fully
accessible? If so:
RESTORE DATABASE dbname WITH RECOVERY
No actual restore is performed, only the recovery work to get it out of standby mode.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in message
news:72D84926-67E3-4A3F-A011-E5F5A6ACA8CC@.microsoft.com...
> Hi
> I am using SQL 2000 std edition and hence using custom scripts to
> restore the DB using standby file. I am backing up T-LOGs every 30 mins on
> production and copying them on a network location which is accessible to
> standby machine.
> I run a job on standby machine which applies the transaction logs every 30
> mins by checking in backmediaset & backupmediafamily tables of Production. DB
> is running in read only and is working.
> Question : In case my Production machine goes down and does not come up how
> can I start the Standby "with data loss" if it has already appiled the last
> T-logs generated on production.
> Since Produciton (primary) is down I can not backup the last T-log.
> Thanks
> Mangesh
>|||Yes. I am doing a continuous restoration of my standby database using standby
file.
Thanks for help.
"Tibor Karaszi" wrote:
> So you are continuously doing RESTORE WITH STANDBY? And you now wand to make the database fully
> accessible? If so:
> RESTORE DATABASE dbname WITH RECOVERY
> No actual restore is performed, only the recovery work to get it out of standby mode.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in message
> news:72D84926-67E3-4A3F-A011-E5F5A6ACA8CC@.microsoft.com...
> > Hi
> >
> > I am using SQL 2000 std edition and hence using custom scripts to
> > restore the DB using standby file. I am backing up T-LOGs every 30 mins on
> > production and copying them on a network location which is accessible to
> > standby machine.
> >
> > I run a job on standby machine which applies the transaction logs every 30
> > mins by checking in backmediaset & backupmediafamily tables of Production. DB
> > is running in read only and is working.
> >
> > Question : In case my Production machine goes down and does not come up how
> > can I start the Standby "with data loss" if it has already appiled the last
> > T-logs generated on production.
> > Since Produciton (primary) is down I can not backup the last T-log.
> >
> > Thanks
> > Mangesh
> >
> >
>
>
Friday, March 9, 2012
Question on installing the SQL Server 2005 Developer Edition on the Windows Vista
I cannot find any specific info on the support of SQL server 2005 developer edition on different Windows Vista. Does anyone have any experience? TIAjust refer, http://msdn2.microsoft.com/en-us/library/ms143506.aspx|||My experience is very problematical. I've tried installing it several times on my new Vista 64 Ultimate machine, and each time I wind up with only the Express edition, not the full/Enterprise edition as I was able to do on my prior XP Professional machine. Being limited to Express is a problem, since the test database I have from my client exceeds the 4GB threshold that the Express Edition imposes. If anyone has had better luck, or knows hoow to do this better, I'd love to hear about it.
Wednesday, March 7, 2012
Question on DEveloper EDition Client Tools Only
Hi:
Our developer's are supposed to use SQL Server Developer Edition Client
Tools Only.
Can anybody tell me if any of the components below could be considered
as that tool?
Many thanks in advance.
Analysis Services Shared Tools
=B7 Business Intelligence Development Studio
=B7 Connectivity Components
=B7 Legacy Components
=B7 Management Tools
=B7 Notification Services Client Components
=B7 Reporting Services Report Manager
=B7 Reporting Services Shared Tools
=B7 SQL Server 2005 Shared Tools
=B7 Software Development Kit
=B7 SQLXML Client Features
=B7 SQL Server 2005 Books Online
=B7 SQL Server Mobile Server ToolsDataPro wrote:
> Hi:
> Our developer's are supposed to use SQL Server Developer Edition Client
> Tools Only.
> Can anybody tell me if any of the components below could be considered
> as that tool?
> Many thanks in advance.
> Analysis Services Shared Tools
> Business Intelligence Development Studio
> Connectivity Components
> Legacy Components
> Management Tools
> Notification Services Client Components
> Reporting Services Report Manager
> Reporting Services Shared Tools
> SQL Server 2005 Shared Tools
> Software Development Kit
> SQLXML Client Features
> SQL Server 2005 Books Online
> SQL Server Mobile Server Tools
>
Those are basic SQL Server components. You're asking the wrong
question, it's not the components that you need to worry about, it's
where they were installed from. Were they installed from SQL Server
Developer Edition media, or one of the other editions?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Our software aquisition folks tell me that they were in the contract as
sub components of SQL Server 2005 Standard and Enterprise Editions.
Does that make sense?
I was told that if one attempted to install SQL Server on a server that
could work. However attempting to install it on a workstation would
only allow the installation of Query Analyzer. So I'm not sure if any
other client tools could be installed that way.
Thanks for the help.
Tracy McKibben wrote:
> DataPro wrote:
> Those are basic SQL Server components. You're asking the wrong
> question, it's not the components that you need to worry about, it's
> where they were installed from. Were they installed from SQL Server
> Developer Edition media, or one of the other editions?
>=20
>=20
> --=20
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
Our developer's are supposed to use SQL Server Developer Edition Client
Tools Only.
Can anybody tell me if any of the components below could be considered
as that tool?
Many thanks in advance.
Analysis Services Shared Tools
=B7 Business Intelligence Development Studio
=B7 Connectivity Components
=B7 Legacy Components
=B7 Management Tools
=B7 Notification Services Client Components
=B7 Reporting Services Report Manager
=B7 Reporting Services Shared Tools
=B7 SQL Server 2005 Shared Tools
=B7 Software Development Kit
=B7 SQLXML Client Features
=B7 SQL Server 2005 Books Online
=B7 SQL Server Mobile Server ToolsDataPro wrote:
> Hi:
> Our developer's are supposed to use SQL Server Developer Edition Client
> Tools Only.
> Can anybody tell me if any of the components below could be considered
> as that tool?
> Many thanks in advance.
> Analysis Services Shared Tools
> Business Intelligence Development Studio
> Connectivity Components
> Legacy Components
> Management Tools
> Notification Services Client Components
> Reporting Services Report Manager
> Reporting Services Shared Tools
> SQL Server 2005 Shared Tools
> Software Development Kit
> SQLXML Client Features
> SQL Server 2005 Books Online
> SQL Server Mobile Server Tools
>
Those are basic SQL Server components. You're asking the wrong
question, it's not the components that you need to worry about, it's
where they were installed from. Were they installed from SQL Server
Developer Edition media, or one of the other editions?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Our software aquisition folks tell me that they were in the contract as
sub components of SQL Server 2005 Standard and Enterprise Editions.
Does that make sense?
I was told that if one attempted to install SQL Server on a server that
could work. However attempting to install it on a workstation would
only allow the installation of Query Analyzer. So I'm not sure if any
other client tools could be installed that way.
Thanks for the help.
Tracy McKibben wrote:
> DataPro wrote:
> Those are basic SQL Server components. You're asking the wrong
> question, it's not the components that you need to worry about, it's
> where they were installed from. Were they installed from SQL Server
> Developer Edition media, or one of the other editions?
>=20
>=20
> --=20
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
Question on DEveloper EDition Client Tools Only
Hi:
Our developer's are supposed to use SQL Server Developer Edition Client
Tools Only.
Can anybody tell me if any of the components below could be considered
as that tool?
Many thanks in advance.
Analysis Services Shared Tools
=B7 Business Intelligence Development Studio
=B7 Connectivity Components
=B7 Legacy Components
=B7 Management Tools
=B7 Notification Services Client Components
=B7 Reporting Services Report Manager
=B7 Reporting Services Shared Tools
=B7 SQL Server 2005 Shared Tools
=B7 Software Development Kit
=B7 SQLXML Client Features
=B7 SQL Server 2005 Books Online
=B7 SQL Server Mobile Server ToolsDataPro wrote:
> Hi:
> Our developer's are supposed to use SQL Server Developer Edition Client
> Tools Only.
> Can anybody tell me if any of the components below could be considered
> as that tool?
> Many thanks in advance.
> Analysis Services Shared Tools
> · Business Intelligence Development Studio
> · Connectivity Components
> · Legacy Components
> · Management Tools
> · Notification Services Client Components
> · Reporting Services Report Manager
> · Reporting Services Shared Tools
> · SQL Server 2005 Shared Tools
> · Software Development Kit
> · SQLXML Client Features
> · SQL Server 2005 Books Online
> · SQL Server Mobile Server Tools
>
Those are basic SQL Server components. You're asking the wrong
question, it's not the components that you need to worry about, it's
where they were installed from. Were they installed from SQL Server
Developer Edition media, or one of the other editions?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Our software aquisition folks tell me that they were in the contract as
sub components of SQL Server 2005 Standard and Enterprise Editions.
Does that make sense?
I was told that if one attempted to install SQL Server on a server that
could work. However attempting to install it on a workstation would
only allow the installation of Query Analyzer. So I'm not sure if any
other client tools could be installed that way.
Thanks for the help.
Tracy McKibben wrote:
> DataPro wrote:
> > Hi:
> >
> > Our developer's are supposed to use SQL Server Developer Edition Client
> > Tools Only.
> >
> > Can anybody tell me if any of the components below could be considered
> > as that tool?
> >
> > Many thanks in advance.
> >
> > Analysis Services Shared Tools
> >
> > =B7 Business Intelligence Development Studio
> >
> > =B7 Connectivity Components
> >
> > =B7 Legacy Components
> >
> > =B7 Management Tools
> >
> > =B7 Notification Services Client Components
> >
> > =B7 Reporting Services Report Manager
> >
> > =B7 Reporting Services Shared Tools
> >
> > =B7 SQL Server 2005 Shared Tools
> >
> > =B7 Software Development Kit
> >
> > =B7 SQLXML Client Features
> >
> > =B7 SQL Server 2005 Books Online
> >
> > =B7 SQL Server Mobile Server Tools
> >
> Those are basic SQL Server components. You're asking the wrong
> question, it's not the components that you need to worry about, it's
> where they were installed from. Were they installed from SQL Server
> Developer Edition media, or one of the other editions?
> > > -- > Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
Our developer's are supposed to use SQL Server Developer Edition Client
Tools Only.
Can anybody tell me if any of the components below could be considered
as that tool?
Many thanks in advance.
Analysis Services Shared Tools
=B7 Business Intelligence Development Studio
=B7 Connectivity Components
=B7 Legacy Components
=B7 Management Tools
=B7 Notification Services Client Components
=B7 Reporting Services Report Manager
=B7 Reporting Services Shared Tools
=B7 SQL Server 2005 Shared Tools
=B7 Software Development Kit
=B7 SQLXML Client Features
=B7 SQL Server 2005 Books Online
=B7 SQL Server Mobile Server ToolsDataPro wrote:
> Hi:
> Our developer's are supposed to use SQL Server Developer Edition Client
> Tools Only.
> Can anybody tell me if any of the components below could be considered
> as that tool?
> Many thanks in advance.
> Analysis Services Shared Tools
> · Business Intelligence Development Studio
> · Connectivity Components
> · Legacy Components
> · Management Tools
> · Notification Services Client Components
> · Reporting Services Report Manager
> · Reporting Services Shared Tools
> · SQL Server 2005 Shared Tools
> · Software Development Kit
> · SQLXML Client Features
> · SQL Server 2005 Books Online
> · SQL Server Mobile Server Tools
>
Those are basic SQL Server components. You're asking the wrong
question, it's not the components that you need to worry about, it's
where they were installed from. Were they installed from SQL Server
Developer Edition media, or one of the other editions?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Our software aquisition folks tell me that they were in the contract as
sub components of SQL Server 2005 Standard and Enterprise Editions.
Does that make sense?
I was told that if one attempted to install SQL Server on a server that
could work. However attempting to install it on a workstation would
only allow the installation of Query Analyzer. So I'm not sure if any
other client tools could be installed that way.
Thanks for the help.
Tracy McKibben wrote:
> DataPro wrote:
> > Hi:
> >
> > Our developer's are supposed to use SQL Server Developer Edition Client
> > Tools Only.
> >
> > Can anybody tell me if any of the components below could be considered
> > as that tool?
> >
> > Many thanks in advance.
> >
> > Analysis Services Shared Tools
> >
> > =B7 Business Intelligence Development Studio
> >
> > =B7 Connectivity Components
> >
> > =B7 Legacy Components
> >
> > =B7 Management Tools
> >
> > =B7 Notification Services Client Components
> >
> > =B7 Reporting Services Report Manager
> >
> > =B7 Reporting Services Shared Tools
> >
> > =B7 SQL Server 2005 Shared Tools
> >
> > =B7 Software Development Kit
> >
> > =B7 SQLXML Client Features
> >
> > =B7 SQL Server 2005 Books Online
> >
> > =B7 SQL Server Mobile Server Tools
> >
> Those are basic SQL Server components. You're asking the wrong
> question, it's not the components that you need to worry about, it's
> where they were installed from. Were they installed from SQL Server
> Developer Edition media, or one of the other editions?
> > > -- > Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
Subscribe to:
Posts (Atom)