I'm using SQL Lightspeed for Log shipping and I keep getting the following r
eturncode when calling their xp_backup_database procedure.
The error message says it's a sql returncode. Is this a syntax returncode?
Any know?
ThanksI havent worked with sql litespeed, but given that transaction log backups
are going on, pls check the sql error logs on both the Primary and
Secondary to see if there is a problem with the tran logs.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Showing posts with label log. Show all posts
Showing posts with label log. Show all posts
Friday, March 30, 2012
Return Code 62309
I'm using SQL Lightspeed for Log shipping and I keep getting the following returncode when calling their xp_backup_database procedure.
The error message says it's a sql returncode. Is this a syntax returncode? Any know?
ThanksI havent worked with sql litespeed, but given that transaction log backups
are going on, pls check the sql error logs on both the Primary and
Secondary to see if there is a problem with the tran logs.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
The error message says it's a sql returncode. Is this a syntax returncode? Any know?
ThanksI havent worked with sql litespeed, but given that transaction log backups
are going on, pls check the sql error logs on both the Primary and
Secondary to see if there is a problem with the tran logs.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Labels:
calling,
code,
database,
error,
following,
lightspeed,
log,
microsoft,
mysql,
oracle,
procedure,
return,
returncode,
server,
shipping,
sql,
xp_backup_database
Return Code 62309
I'm using SQL Lightspeed for Log shipping and I keep getting the following returncode when calling their xp_backup_database procedure.
The error message says it's a sql returncode. Is this a syntax returncode? Any know?
Thanks
I havent worked with sql litespeed, but given that transaction log backups
are going on, pls check the sql error logs on both the Primary and
Secondary to see if there is a problem with the tran logs.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
sql
The error message says it's a sql returncode. Is this a syntax returncode? Any know?
Thanks
I havent worked with sql litespeed, but given that transaction log backups
are going on, pls check the sql error logs on both the Primary and
Secondary to see if there is a problem with the tran logs.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
sql
Labels:
calling,
code,
database,
error,
following,
lightspeed,
log,
microsoft,
mysql,
oracle,
procedure,
return,
returncode,
server,
shipping,
sql,
xp_backup_database
Monday, March 12, 2012
Retrieving data from .MDF?
Dear fellows,
Up to the moment I've got enough knowledge for read data stored into .LDF files by dbcc log and so on. It's very useful and interesting. Now, I wonder how to retrieve the same information but on MDF files.
At first, I want to make sure that is not possible by mean of traditional methods (dbcc or something like that) I suppose so but I'd like to hear opinions regarding that.
Thanks in advance for any idea, though or further information.
Enric,
We don't support reverse engineering the data from .mdf files in general, however we license our API's to third party vendors so that they can build tools to support these types of disaster recovery operations.
-Matt
|||Thanks a lot|||If you're just interested in poking about though, checkout this link.Friday, March 9, 2012
Retrieveing objects
Dears,
I created a table, then dropped it by mistake. Is there any way to retrieve it back using the log file? The lat DB backup was made before creating the table.
Thanks,1. Take a log backup
2. make another database and restore the previous full backup over there as you would not want to make any changes to the original db
3. restore transaction log to a time before you dropped the table
4. copy table onto original database
tell me if you need any other help|||When applying the backup, through the Enterprise Manager, I had the "Point in time restore" option disabled. Have an idea why? Do you think making the backup through the T-SQL better?
Originally posted by Enigma
1. Take a log backup
2. make another database and restore the previous full backup over there as you would not want to make any changes to the original db
3. restore transaction log to a time before you dropped the table
4. copy table onto original database
tell me if you need any other help|||Question : What is your database recovery model
Simple , Full or Bulk Logged
Give me a list of the things you have done till now ...
I created a table, then dropped it by mistake. Is there any way to retrieve it back using the log file? The lat DB backup was made before creating the table.
Thanks,1. Take a log backup
2. make another database and restore the previous full backup over there as you would not want to make any changes to the original db
3. restore transaction log to a time before you dropped the table
4. copy table onto original database
tell me if you need any other help|||When applying the backup, through the Enterprise Manager, I had the "Point in time restore" option disabled. Have an idea why? Do you think making the backup through the T-SQL better?
Originally posted by Enigma
1. Take a log backup
2. make another database and restore the previous full backup over there as you would not want to make any changes to the original db
3. restore transaction log to a time before you dropped the table
4. copy table onto original database
tell me if you need any other help|||Question : What is your database recovery model
Simple , Full or Bulk Logged
Give me a list of the things you have done till now ...
Wednesday, March 7, 2012
Retrieve the logical file name from a backup device
Hi,
I'm working on some "daemon" able to restore whatever come into a given
folder to a "stand-by" SQL Server (sort of log shipping, but also to restore
full backup and so on).
I'm now faing a problem : I can't put the logical name of the database from
the backup file to a variable.
Here a sample of what I 'm trying to do :
--
DECLARE @.Data_file nvarchar (256)
create table #result
(
LogicalName varchar(512),
PhysicalName varchar(512),
Type varchar(1),
FileGroupName nvarchar(50),
Size int,
Maxsize int
)
insert into #result EXEC (restore filelistonly from disk='X:\file.bak')
--
(please note that table declaration, variable delclaration, etc may be
weird, but it's purely test code to try validate my concept.
Each time I got the following error :
Server: Msg 156, Level 15, State 1, Line 1
Incorrect syntax near the keyword 'restore'.
Server: Msg 170, Level 15, State 1, Line 1
Line 1: Incorrect syntax near ')'.
As RESTORE filelistonly is, from BOL, returning a dataset, I was expecting
to be able to load into a table, or to be able to extract data from it
easily.
I do not know where to look at, any help will be welcome,
Thanks,
ChrisSee "RESTORE FILELISTONLY " in BOL.
AMB
"Chris V." wrote:
> Hi,
> I'm working on some "daemon" able to restore whatever come into a given
> folder to a "stand-by" SQL Server (sort of log shipping, but also to resto
re
> full backup and so on).
> I'm now faing a problem : I can't put the logical name of the database fro
m
> the backup file to a variable.
> Here a sample of what I 'm trying to do :
> --
> DECLARE @.Data_file nvarchar (256)
> create table #result
> (
> LogicalName varchar(512),
> PhysicalName varchar(512),
> Type varchar(1),
> FileGroupName nvarchar(50),
> Size int,
> Maxsize int
> )
> insert into #result EXEC (restore filelistonly from disk='X:\file.bak')
> --
> (please note that table declaration, variable delclaration, etc may be
> weird, but it's purely test code to try validate my concept.
> Each time I got the following error :
> Server: Msg 156, Level 15, State 1, Line 1
> Incorrect syntax near the keyword 'restore'.
> Server: Msg 170, Level 15, State 1, Line 1
> Line 1: Incorrect syntax near ')'.
>
> As RESTORE filelistonly is, from BOL, returning a dataset, I was expecting
> to be able to load into a table, or to be able to extract data from it
> easily.
> I do not know where to look at, any help will be welcome,
> Thanks,
> Chris
>
>|||Hi Alejandro,
That's what I;ve done, bout couldn't find the way to have the following
result :
SELECT @.DATE_FILE =SELECT LogicalName from EXEC(RESTORE FILELISTONLY from
DISK='File') where TYPE='D'
I'm desperate :)
Thanks,
Chris
"Alejandro Mesa" <AlejandroMesa@.discussions.microsoft.com> a crit dans le
message de news:99C7DE87-8022-4F37-A797-F99296625772@.microsoft.com...
> See "RESTORE FILELISTONLY " in BOL.
>
> AMB
> "Chris V." wrote:
>
restore
from
expecting|||Try,
use northwind
go
create table #t (
LogicalName sysname,
PhysicalName sysname,
Type char(1),
FileGroupName sysname null,
[Size] bigint,
[MaxSize] bigint
)
insert into #t
execute sp_executesql N'use master restore filelistonly from mydump'
select
*
from
#t
drop table #t
go
AMB
"Chris" wrote:
> Hi Alejandro,
> That's what I;ve done, bout couldn't find the way to have the following
> result :
> SELECT @.DATE_FILE =SELECT LogicalName from EXEC(RESTORE FILELISTONLY from
> DISK='File') where TYPE='D'
> I'm desperate :)
> Thanks,
> Chris
> "Alejandro Mesa" <AlejandroMesa@.discussions.microsoft.com> a écrit dans l
e
> message de news:99C7DE87-8022-4F37-A797-F99296625772@.microsoft.com...
> restore
> from
> expecting
>
>|||Works perfectly !
Thanks
"Alejandro Mesa" <AlejandroMesa@.discussions.microsoft.com> wrote in message
news:E686C7EB-957F-4A14-BEA2-6C86F80B1D3F@.microsoft.com...
> Try,
> use northwind
> go
> create table #t (
> LogicalName sysname,
> PhysicalName sysname,
> Type char(1),
> FileGroupName sysname null,
> [Size] bigint,
> [MaxSize] bigint
> )
> insert into #t
> execute sp_executesql N'use master restore filelistonly from mydump'
> select
> *
> from
> #t
> drop table #t
> go
>
> AMB
> "Chris" wrote:
>
from
le
given
database
disk='X:\file.bak')
be
it
I'm working on some "daemon" able to restore whatever come into a given
folder to a "stand-by" SQL Server (sort of log shipping, but also to restore
full backup and so on).
I'm now faing a problem : I can't put the logical name of the database from
the backup file to a variable.
Here a sample of what I 'm trying to do :
--
DECLARE @.Data_file nvarchar (256)
create table #result
(
LogicalName varchar(512),
PhysicalName varchar(512),
Type varchar(1),
FileGroupName nvarchar(50),
Size int,
Maxsize int
)
insert into #result EXEC (restore filelistonly from disk='X:\file.bak')
--
(please note that table declaration, variable delclaration, etc may be
weird, but it's purely test code to try validate my concept.
Each time I got the following error :
Server: Msg 156, Level 15, State 1, Line 1
Incorrect syntax near the keyword 'restore'.
Server: Msg 170, Level 15, State 1, Line 1
Line 1: Incorrect syntax near ')'.
As RESTORE filelistonly is, from BOL, returning a dataset, I was expecting
to be able to load into a table, or to be able to extract data from it
easily.
I do not know where to look at, any help will be welcome,
Thanks,
ChrisSee "RESTORE FILELISTONLY " in BOL.
AMB
"Chris V." wrote:
> Hi,
> I'm working on some "daemon" able to restore whatever come into a given
> folder to a "stand-by" SQL Server (sort of log shipping, but also to resto
re
> full backup and so on).
> I'm now faing a problem : I can't put the logical name of the database fro
m
> the backup file to a variable.
> Here a sample of what I 'm trying to do :
> --
> DECLARE @.Data_file nvarchar (256)
> create table #result
> (
> LogicalName varchar(512),
> PhysicalName varchar(512),
> Type varchar(1),
> FileGroupName nvarchar(50),
> Size int,
> Maxsize int
> )
> insert into #result EXEC (restore filelistonly from disk='X:\file.bak')
> --
> (please note that table declaration, variable delclaration, etc may be
> weird, but it's purely test code to try validate my concept.
> Each time I got the following error :
> Server: Msg 156, Level 15, State 1, Line 1
> Incorrect syntax near the keyword 'restore'.
> Server: Msg 170, Level 15, State 1, Line 1
> Line 1: Incorrect syntax near ')'.
>
> As RESTORE filelistonly is, from BOL, returning a dataset, I was expecting
> to be able to load into a table, or to be able to extract data from it
> easily.
> I do not know where to look at, any help will be welcome,
> Thanks,
> Chris
>
>|||Hi Alejandro,
That's what I;ve done, bout couldn't find the way to have the following
result :
SELECT @.DATE_FILE =SELECT LogicalName from EXEC(RESTORE FILELISTONLY from
DISK='File') where TYPE='D'
I'm desperate :)
Thanks,
Chris
"Alejandro Mesa" <AlejandroMesa@.discussions.microsoft.com> a crit dans le
message de news:99C7DE87-8022-4F37-A797-F99296625772@.microsoft.com...
> See "RESTORE FILELISTONLY " in BOL.
>
> AMB
> "Chris V." wrote:
>
restore
from
expecting|||Try,
use northwind
go
create table #t (
LogicalName sysname,
PhysicalName sysname,
Type char(1),
FileGroupName sysname null,
[Size] bigint,
[MaxSize] bigint
)
insert into #t
execute sp_executesql N'use master restore filelistonly from mydump'
select
*
from
#t
drop table #t
go
AMB
"Chris" wrote:
> Hi Alejandro,
> That's what I;ve done, bout couldn't find the way to have the following
> result :
> SELECT @.DATE_FILE =SELECT LogicalName from EXEC(RESTORE FILELISTONLY from
> DISK='File') where TYPE='D'
> I'm desperate :)
> Thanks,
> Chris
> "Alejandro Mesa" <AlejandroMesa@.discussions.microsoft.com> a écrit dans l
e
> message de news:99C7DE87-8022-4F37-A797-F99296625772@.microsoft.com...
> restore
> from
> expecting
>
>|||Works perfectly !
Thanks
"Alejandro Mesa" <AlejandroMesa@.discussions.microsoft.com> wrote in message
news:E686C7EB-957F-4A14-BEA2-6C86F80B1D3F@.microsoft.com...
> Try,
> use northwind
> go
> create table #t (
> LogicalName sysname,
> PhysicalName sysname,
> Type char(1),
> FileGroupName sysname null,
> [Size] bigint,
> [MaxSize] bigint
> )
> insert into #t
> execute sp_executesql N'use master restore filelistonly from mydump'
> select
> *
> from
> #t
> drop table #t
> go
>
> AMB
> "Chris" wrote:
>
from
le
given
database
disk='X:\file.bak')
be
it
Tuesday, February 21, 2012
Retrieve Deleted Items > Log
Looking for a little assistance with a big problem.
I lost some data from a query that went wrong. I still have the logfile though, is there anyway of retrieving the data from the log file (.LDF) so that I can undo what someone did?
I located some 3rd party software but they are big bucks and the demos won't allow you to do it..
Thanks in advance,
JayThe safest thing would be to backup the transaction log, then restore the database froma full backup with norecovery, then restore the transaction log with 'stopat = time' where time is just before the bad query was run. This assumes that you are in full recovery mode, however.
Alternatively, if you have the disk space, you can restore the database to a new location, and try to transfer some of the lost data over. This is much more risky, as you have to be sure you get all of the relationships, id values, etc. right. Most vendors will invalidate their support contracts, if you do this sort of thing to their databases.
I lost some data from a query that went wrong. I still have the logfile though, is there anyway of retrieving the data from the log file (.LDF) so that I can undo what someone did?
I located some 3rd party software but they are big bucks and the demos won't allow you to do it..
Thanks in advance,
JayThe safest thing would be to backup the transaction log, then restore the database froma full backup with norecovery, then restore the transaction log with 'stopat = time' where time is just before the bad query was run. This assumes that you are in full recovery mode, however.
Alternatively, if you have the disk space, you can restore the database to a new location, and try to transfer some of the lost data over. This is much more risky, as you have to be sure you get all of the relationships, id values, etc. right. Most vendors will invalidate their support contracts, if you do this sort of thing to their databases.
Subscribe to:
Posts (Atom)