MSSQL7

I am a beginner with MSSQL7 so please bear with me. I am trying to open a
database that is approx 187KB in size. This file resides in the following
folder; C:\MSSQL7\DATA. This was restored from a backup we reterived from a
subjects computer. I obtained a copy of the MSSQL7 software. I was able to
load it on a standalone computer. This is as far as I can get. I want to be
able to copy the 187KB file in the approporiate folder of this newley
installed MSSQL7 program so I can simply open up the tables and see the data.
When I start Enterprise manager, I can't seem to connect it to this old
database.
Please help
cart34@.netzero.net
Have a look at these. You can use sp_attach_db to add it to the new server.
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465 Using WITH MOVE in a
Restore
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scri...p?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
Andrew J. Kelly SQL MVP
"Cart34" <Cart34@.discussions.microsoft.com> wrote in message
news:522E836E-979C-4D80-8823-949D3148A6A9@.microsoft.com...
>I am a beginner with MSSQL7 so please bear with me. I am trying to open a
> database that is approx 187KB in size. This file resides in the following
> folder; C:\MSSQL7\DATA. This was restored from a backup we reterived from
> a
> subjects computer. I obtained a copy of the MSSQL7 software. I was able
> to
> load it on a standalone computer. This is as far as I can get. I want to
> be
> able to copy the 187KB file in the approporiate folder of this newley
> installed MSSQL7 program so I can simply open up the tables and see the
> data.
> When I start Enterprise manager, I can't seem to connect it to this old
> database.
> Please help
> cart34@.netzero.net

MSSQL Server Backups

I would like to modify the amount of backups that the sql server keeps on
record. My reasoning is that I am trying to minimize the size of my full
backups. I was made aware that the server keeps a certain time period of
backups and that I could modify this and lessen the time period that it keeps
backups. I hope this makes sense. Thanks in advance.
hi,
cc.az wrote:
> I would like to modify the amount of backups that the sql server
> keeps on record. My reasoning is that I am trying to minimize the
> size of my full backups. I was made aware that the server keeps a
> certain time period of backups and that I could modify this and
> lessen the time period that it keeps backups. I hope this makes
> sense. Thanks in advance.
all the retaintion for backups can be set manually in the Backup
operation...
you can specify the
RETAINDAYS = 1 -- no of days
or
EXPIREDATE = N'2005/02/03' -- an actual date...
if those 2 settings are not provided, the default expiration is determined
by the media retention configuration setting of sp_configure..
http://msdn.microsoft.com/library/de...ba-bz_35ww.asp
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSSQL questions

1) I haven't seen any use of "SAVE TRANSACTION" in small to mid size apps. Is it used mainly in big and complex apps?

2) Given this linkhttp://www.databasejournal.com/features/mssql/article.php/3584751 about SQL2005. How can what the article presents be done in SQL2000?

Thanks.

SAVE TRANSACTION isn't normally used in small apps because you would only want to use it in a situation in which you have a subroutine that might fail, but you still want the transaction to commit. Small apps usually either have very small transactions (or none), and you either want them to commit or rollback as a single unit. I've used it in mid size apps where I was looping, doing some processing of for a batch transaction, and any loop may fail, but I needed it to skip the bad loop and continue processing. This isn't very common.

For example a batch load of (something), as you are looping through, Save trans, insert, save trans, insert (Insert fails) rollback, save trans, insert, commit.

Record #1, and #3 are commited to the database, while record #2 failed and was rolled back. Many times this type of logic can also be subdivided into separate transactions (BEGIN TRANS, insert, commit, begin trans, insert (fail), rollback, begin trans, insert, commit), but in some cases it can't. It's those rare cases in which save transaction is nice.

|||Please take a look at my second question and advise? Thanks.|||Can't really help you out there very much. In the past I've written my own .NET apps that monitored directories for file drops and sucked them into the database. Never used the bulk load stuff for that as I don't think it's a great idea to give access to the SQL Server itself for file drops.