Showing posts with label live. Show all posts
Showing posts with label live. Show all posts

Thursday, February 16, 2012

Backup without tabledata

Hello.

I am using SQL express and we have developed our app. til now.

Now we have to move the database to the another server and go live. It is fine just to backup the database but how to do it without tabledata? We have many test posts there and when going live we would like to start from beginning.

Is there any way to do it or do we have to delete all data before backing up?

Hi

This is possible. Under MSSQL 2005 Management Studio select the Database > All Tasks > Generate Script and Walk thru the all options.

Doing this will generate the script which you can use on empty database to get the tables etc.

Thanks

Rubal Jain

|||Hi!

Isn't there any Export function in SQL Express or MSSQL 2005 Management Studio?

Monday, February 13, 2012

Backup up warm-standby server

Hello all-
We have a two databases, BoxA and BoxB. BoxA is the live production server
and BoxB is a backup server that we do log shipping to.
Every couple of hours we ship logs from BoxA to BoxB. BoxB is a warm
standby SQL server.
We would like to backup BoxB, the warm standby, however we receive the
following error message:
"
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3036: [Microsoft][ODBC SQL
Server Driver][SQL Server]Database '' is in warm-standby state (set by
executing RESTORE WITH STANDBY) and cannot be backed up until the entire
load sequence is completed.
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is
terminating abnormally.
"
Now is there any easy way to backup the database on BoxB without dropping
the maintenance plans?
Any help would be greatly appreciated.
We just had a discussion about this. See the thread "How can I backup a log-shipped database?".
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"anonymous" <a@.b.bad> wrote in message news:%23QWkYf5jEHA.3852@.tk2msftngp13.phx.gbl...
> Hello all-
> We have a two databases, BoxA and BoxB. BoxA is the live production server
> and BoxB is a backup server that we do log shipping to.
> Every couple of hours we ship logs from BoxA to BoxB. BoxB is a warm
> standby SQL server.
> We would like to backup BoxB, the warm standby, however we receive the
> following error message:
> "
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3036: [Microsoft][ODBC SQL
> Server Driver][SQL Server]Database '' is in warm-standby state (set by
> executing RESTORE WITH STANDBY) and cannot be backed up until the entire
> load sequence is completed.
> [Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is
> terminating abnormally.
> "
> Now is there any easy way to backup the database on BoxB without dropping
> the maintenance plans?
> Any help would be greatly appreciated.
>
|||Instead of trying to backup the database that is constantly recovering, why
not add another target server to your logshipping configuration?
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"anonymous" <a@.b.bad> wrote in message
news:%23QWkYf5jEHA.3852@.tk2msftngp13.phx.gbl...
> Hello all-
> We have a two databases, BoxA and BoxB. BoxA is the live production
server
> and BoxB is a backup server that we do log shipping to.
> Every couple of hours we ship logs from BoxA to BoxB. BoxB is a warm
> standby SQL server.
> We would like to backup BoxB, the warm standby, however we receive the
> following error message:
> "
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3036: [Microsoft][ODBC
SQL
> Server Driver][SQL Server]Database '' is in warm-standby state (set by
> executing RESTORE WITH STANDBY) and cannot be backed up until the entire
> load sequence is completed.
> [Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is
> terminating abnormally.
> "
> Now is there any easy way to backup the database on BoxB without dropping
> the maintenance plans?
> Any help would be greatly appreciated.
>

Backup up warm-standby server

Hello all-
We have a two databases, BoxA and BoxB. BoxA is the live production server
and BoxB is a backup server that we do log shipping to.
Every couple of hours we ship logs from BoxA to BoxB. BoxB is a warm
standby SQL server.
We would like to backup BoxB, the warm standby, however we receive the
following error message:
"
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3036: [Microsoft]&#
91;ODBC SQL
Server Driver][SQL Server]Database '' is in warm-standby state (set by
executing RESTORE WITH STANDBY) and cannot be backed up until the entire
load sequence is completed.
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE i
s
terminating abnormally.
"
Now is there any easy way to backup the database on BoxB without dropping
the maintenance plans?
Any help would be greatly appreciated.We just had a discussion about this. See the thread "How can I backup a log-
shipped database?".
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"anonymous" <a@.b.bad> wrote in message news:%23QWkYf5jEHA.3852@.tk2msftngp13.phx.gbl...[vbcol
=seagreen]
> Hello all-
> We have a two databases, BoxA and BoxB. BoxA is the live production serve
r
> and BoxB is a backup server that we do log shipping to.
> Every couple of hours we ship logs from BoxA to BoxB. BoxB is a warm
> standby SQL server.
> We would like to backup BoxB, the warm standby, however we receive the
> following error message:
> "
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3036: [Microsoft]
[ODBC SQL
> Server Driver][SQL Server]Database '' is in warm-standby state (set by
> executing RESTORE WITH STANDBY) and cannot be backed up until the entire
> load sequence is completed.
> [Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE
is
> terminating abnormally.
> "
> Now is there any easy way to backup the database on BoxB without dropping
> the maintenance plans?
> Any help would be greatly appreciated.
>[/vbcol]|||Instead of trying to backup the database that is constantly recovering, why
not add another target server to your logshipping configuration?
--
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"anonymous" <a@.b.bad> wrote in message
news:%23QWkYf5jEHA.3852@.tk2msftngp13.phx.gbl...
> Hello all-
> We have a two databases, BoxA and BoxB. BoxA is the live production
server
> and BoxB is a backup server that we do log shipping to.
> Every couple of hours we ship logs from BoxA to BoxB. BoxB is a warm
> standby SQL server.
> We would like to backup BoxB, the warm standby, however we receive the
> following error message:
> "
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3036: [Microsoft][ODB
C
SQL
> Server Driver][SQL Server]Database '' is in warm-standby state (set by
> executing RESTORE WITH STANDBY) and cannot be backed up until the entire
> load sequence is completed.
> [Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE
is
> terminating abnormally.
> "
> Now is there any easy way to backup the database on BoxB without dropping
> the maintenance plans?
> Any help would be greatly appreciated.
>

Backup up warm-standby server

Hello all-
We have a two databases, BoxA and BoxB. BoxA is the live production server
and BoxB is a backup server that we do log shipping to.
Every couple of hours we ship logs from BoxA to BoxB. BoxB is a warm
standby SQL server.
We would like to backup BoxB, the warm standby, however we receive the
following error message:
"
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3036: [Microsoft][ODBC SQL
Server Driver][SQL Server]Database '' is in warm-standby state (set by
executing RESTORE WITH STANDBY) and cannot be backed up until the entire
load sequence is completed.
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is
terminating abnormally.
"
Now is there any easy way to backup the database on BoxB without dropping
the maintenance plans?
Any help would be greatly appreciated.We just had a discussion about this. See the thread "How can I backup a log-shipped database?".
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"anonymous" <a@.b.bad> wrote in message news:%23QWkYf5jEHA.3852@.tk2msftngp13.phx.gbl...
> Hello all-
> We have a two databases, BoxA and BoxB. BoxA is the live production server
> and BoxB is a backup server that we do log shipping to.
> Every couple of hours we ship logs from BoxA to BoxB. BoxB is a warm
> standby SQL server.
> We would like to backup BoxB, the warm standby, however we receive the
> following error message:
> "
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3036: [Microsoft][ODBC SQL
> Server Driver][SQL Server]Database '' is in warm-standby state (set by
> executing RESTORE WITH STANDBY) and cannot be backed up until the entire
> load sequence is completed.
> [Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is
> terminating abnormally.
> "
> Now is there any easy way to backup the database on BoxB without dropping
> the maintenance plans?
> Any help would be greatly appreciated.
>|||Instead of trying to backup the database that is constantly recovering, why
not add another target server to your logshipping configuration?
--
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"anonymous" <a@.b.bad> wrote in message
news:%23QWkYf5jEHA.3852@.tk2msftngp13.phx.gbl...
> Hello all-
> We have a two databases, BoxA and BoxB. BoxA is the live production
server
> and BoxB is a backup server that we do log shipping to.
> Every couple of hours we ship logs from BoxA to BoxB. BoxB is a warm
> standby SQL server.
> We would like to backup BoxB, the warm standby, however we receive the
> following error message:
> "
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3036: [Microsoft][ODBC
SQL
> Server Driver][SQL Server]Database '' is in warm-standby state (set by
> executing RESTORE WITH STANDBY) and cannot be backed up until the entire
> load sequence is completed.
> [Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is
> terminating abnormally.
> "
> Now is there any easy way to backup the database on BoxB without dropping
> the maintenance plans?
> Any help would be greatly appreciated.
>