Only options you have are FULL, DIFFERENTIAL, TRANSACTION LOG, and
FILEGROUP. If you had had the foresight to create a separate file group
for each table and then ran FILEGROUP backups on each one, then you
might have that as a possibility; however, the administrative overhead
of that scenario is absurd.
You are better off taking your full database backup and restoring to a
new database name; then, you can just extract the table you are after
and move it or the contents to wherever you need it.
Sincerely,
Anthony Thomas, MCDBA, MCSA
-----Original Message-----
From: Lydia Wilson
[mailto:mssqldba-ezmlmshield-x46276899.[Email address protected]
Sent: Thursday, July 29, 2004 6:27 AM
To: LazyDBA Discussion
Subject: Restore : Only one table ??
Hi All
I don't find a option in BOL to restore only one table from a database
backup - Is it possible??
Lydia Wilson
Database Administrator
email: [Email address protected]
Tel: +27 (0) 12 426 5226
Cell: +27 (0) 82 374 4382
-----Original Message-----
From: Entena Raymond
[mailto:mssqldba-ezmlmshield-x27081534.[Email address protected]
Sent: Thursday, July 29, 2004 12:15 PM
To: LazyDBA Discussion
Subject: RE: same temporary table and cursor names running on different
DBs and same server
many thanks guys for the reminders!!
-----Original Message-----
From: Franz Zoister
[mailto:mssqldba-ezmlmshield-x86737078.[Email address protected]
Sent: Thursday, July 29, 2004 6:14 PM
To: LazyDBA Discussion
Subject: RE: same temporary table and cursor names running on different
DBs and same server
And for cursors you should use the addiditional option LOCAL to be sure
that the cursor is private for the connection.
If you dont use this explicitely then it defaullts to the database
option 'default to local cursor'.
regards FZ
-----Original Message-----
From: Daniel Morphett
[mailto:mssqldba-ezmlmshield-x5702011.[Email address protected]
Sent: Donnerstag, 29. Juli 2004 09:17
To: LazyDBA Discussion
Subject: RE: same temporary table and cursor names running on different
DBs and same server
This is off the top of my head, so check it.
If you use global temp tables i.e. ##temp, I think you might run into
trouble, because the double hash sign means it can be read by more than
one connection. So I would restrict your procs to using a local temp
table (one hash in name: #temp). However, you won't be able to use this
if your proc calls another proc that also needs to refer to the temp
table, because it will then be out of scope.
Best thing to do is to try creating the temp table from one db, and then
try reading it from the other (or read BOL on subject)
Daniel Morphett
DBA
Brilliant Digital Entertainment
02 9281 9272
-----Original Message-----
From: Entena Raymond
[mailto:mssqldba-ezmlmshield-x63384665.[Email address protected]
Sent: Thursday, July 29, 2004 5:09 PM
To: LazyDBA Discussion
Subject: FW: same temporary table and cursor names running on different
DBs and same server
Hi,
Any thoughts on my concern below?
Thanks,
Ray
-----Original Message-----
From: Entena, Raymond
Sent: Thursday, July 29, 2004 10:43 AM
To: '[Email address protected]
Subject: same temporary table and cursor names running on different DBs
and same server
Hi Guys,
I have the same set of stored procedure running on different DBs on the
same server. This stored procedure is using temp tables and cursors.
The stored procedure will be scheduled to run everyday, synchronously.
Would this cause data and stored procedure inconsistencies considering
it's declaring the same set of temp tables and cursors?
Thanks in advance.
Ray
---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
Website : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
For additional commands, e-mail: mssqldba-[Email address protected]
---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
Website : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
For additional commands, e-mail: mssqldba-[Email address protected]
---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
Website : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
For additional commands, e-mail: mssqldba-[Email address protected]
---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
Website : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
For additional commands, e-mail: mssqldba-[Email address protected]
______________________________________________
" This email communication and any attachments are confidential and
are intended only for the
individual(s) or entity named above and others who have been
specifically authorized to receive it.
If you are not the intended recipient, please do not copy, use or
disclose the contents of this
communication to others. Please notify the sender that you have
received this email in error by
replying to the email or by telephoning the sender. Please then delete
the email and any copies of
it. This information may contain private, confidential or privileged
material. Thank you."
---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
Website : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
For additional commands, e-mail: mssqldba-[Email address protected]
***********************************************************************
NOTICE: This electronic mail message and any attached files are
confidential. The information is exclusively for the use of the
individual or entity intended as the recipient. If you are not the
intended recipient, any use, copying, printing, reviewing, retention,
disclosure, distribution or forwarding of the message or any attached
file is not authorized and is strictly prohibited. If you have received
this electronic mail message in error, please advise the sender by reply
electronic mail immediately and permanently delete the original
transmission, any attachments and any copies of this message from your
computer system.
***********************************************************************
MS Sql Server LazyDBA home page