Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+MS\-SQL\s+TDP\s+log\s+restore\s+question\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+MS\-SQL\s+TDP\s+log\s+restore\s+question\s*$/: 3 ]

Total 3 documents matching your query.

1. [ADSM-L] MS-SQL TDP log restore question (score: 1): Author: Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>; Date: Thu, 8 Oct 2009 08:10:32 -0400; My MS-SQL guy has the following question and was hoping some TDP experts can give us an answer, one way or the other: "We have an issue that may require physically looking through an old transaction; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-10/msg00093.html (10,985 bytes)
2. Re: [ADSM-L] MS-SQL TDP log restore question (score: 1): Author: David McClelland <tsm AT NETWORKC.CO DOT UK>; Date: Thu, 8 Oct 2009 13:20:01 +0100; I haven't done this myself, but I'd hazard a guess that if there's no standard way of doing it from the TDPSQL GUI (I don't have it in front of me, but I don't recall that there is...) the standard T; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-10/msg00094.html (11,974 bytes)
3. Re: [ADSM-L] MS-SQL TDP log restore question (score: 1): Author: Del Hoobler <hoobler AT US.IBM DOT COM>; Date: Thu, 8 Oct 2009 08:40:42 -0400; In performing backups, the SQL Server simply gives DP/SQL a stream of bytes. The DP/SQL code is not told which files these bytes are from, it is simply a stream of bytes. At restore time, DP/SQL hand; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-10/msg00095.html (12,463 bytes)

Current List: 1 - 3
Page: [1]