Re: How critical is the transaction log file?
- From: "Rick Byham, \(MSFT\)" <rickbyh@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 20 Mar 2008 15:08:04 -0700
The question, is how is SQL Server shut down? When SQL Server shuts down normally, transactions are allowed to complete. Either they succeed and are posted to the database, or fail and are rolled back. If that happens normally, then SQL Server is in a consistent state, and a new log can be created.
On the other hand, if SQL Server shuts down some other way, say a power failure, then transactions may be partially complete. Then the log is critical, to roll back transactions that did not finish.
Naturally Microsoft want to make sure no one ever get's into a jam by having an inconsistent database and no log, so that's not recommended. So send the log, just to be sure.
But the point about using a backup is well taken. Say your database is 100 MB, but only has 70 MB of data, if you send the files you send 100 MB. If you send a backup, you only send the occupied portion of the database, 70 MB. So, sending a backup would be inherently more efficient.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tibor Karaszi" <tibor_please.no.email_karaszi@xxxxxxxxxxxxxxxxxx> wrote in message news:DC24034C-8AA8-44E9-BE76-F54AD260E38A@xxxxxxxxxxxxxxxx
I would like to give justification to the department of not needing it if
there is.
I'm not sure where you are heading with above. To me it is simple. You don't want to do something which isn't supported according to the product documentation. And, btw, I agree with the other post that a backup might be preferable...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"jonefer" <jonefer@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:7268AFB4-E21E-413C-ACC6-DC168D9C9782@xxxxxxxxxxxxxxxxI just realized that I didn't specify - SQL Server 2000, not that that makes
a difference, but I checked the documentation and it only specifies that you
can do it.
Are you talking about the prerequisite of having detached it?
I would like to give justification to the department of not needing it if
there is.
If there isn't, then I'll just go ahead and send 2 files.
"Tibor Karaszi" wrote:
Check out the documentation for sp_attach_single_file_db. This is what you use to attach a database
file when you have only one file (no log file). This documentation will tell you under what
circumstances it is supported to attach only an mdf file.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"jonefer" <jonefer@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9C4245C8-8812-4623-ADE2-322D5C84AB72@xxxxxxxxxxxxxxxx
> For deployment purposes, our IT department has allowed us to send an > mdf file
> to 'attach' to their server in the interim until our own server gets > built.
>
> This development database that we're building does not have any 'user'
> writes to the database, i.e. only DTS will add data to the database.
>
> I've sent the mdf file, 2 weeks in a row not remembering to send the > log
> file, but I've recieved no complates from the IT department and they > seem to
> have managed ok without the file. And the application runs without a > hitch.
>
> I just wondered about ths because finally, somone said something.
> Since we are in a 'development' mode, is this ok? Or should we begin
> sending the transaction log file.
.
- References:
- Re: How critical is the transaction log file?
- From: Tibor Karaszi
- Re: How critical is the transaction log file?
- Prev by Date: Re: How critical is the transaction log file?
- Next by Date: Re: SSIS Import/Export Wizard and DTSWizard doesn't works in SQL 2005
- Previous by thread: Re: How critical is the transaction log file?
- Next by thread: Re: SSIS Import/Export Wizard and DTSWizard doesn't works in SQL 2005
- Index(es):
Relevant Pages
|
Loading
