|
Home > Archive > MS SQL Server > March 2006 > Logfile wish
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Marius Horak 2006-03-10, 7:23 am |
| Dear M$,
Can you get rid off Logfile in your next release of SQL Server, please.
It's pain in neck and 30 year old technology.
MH
| |
| David Portas 2006-03-10, 7:23 am |
| Marius Horak wrote:
> Dear M$,
>
> Can you get rid off Logfile in your next release of SQL Server, please.
> It's pain in neck and 30 year old technology.
>
> MH
That is a very strange request. What problems are you having with the
the log? How do you suggest ACID and transaction-level backups should
be implemented? Other DBMSs that I'm aware of all use the same
technology (maybe under different names). Do you have an alternative?
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--
| |
| Sreejith G 2006-03-10, 7:23 am |
| Innovation happens with these kinda strange thoughts... :) but you should
come up with alternatives when stating such strong comments...
--
Thanks,
Sree
[Please specify the version of Sql Server as we can save one thread and time
asking back if its 2000 or 2005]
"David Portas" wrote:
> Marius Horak wrote:
>
> That is a very strange request. What problems are you having with the
> the log? How do you suggest ACID and transaction-level backups should
> be implemented? Other DBMSs that I'm aware of all use the same
> technology (maybe under different names). Do you have an alternative?
>
> --
> David Portas, SQL Server MVP
>
> Whenever possible please post enough code to reproduce your problem.
> Including CREATE TABLE and INSERT statements usually helps.
> State what version of SQL Server you are using and specify the content
> of any error messages.
>
> SQL Server Books Online:
> http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
> --
>
>
| |
| Marius Horak 2006-03-10, 11:23 am |
| David Portas wrote:
> That is a very strange request.
And what strange about it?
> What problems are you having with the log?
Backup/restore/space
> How do you suggest ACID and transaction-level backups should
> be implemented?
Without a logfile.
> Other DBMSs that I'm aware of all use the same technology (maybe
under different names). Do you have an alternative?
Technology used by Iterbase.
MH
| |
| Tibor Karaszi 2006-03-10, 11:23 am |
| The suggested place to suggest product features and changes is in
http://lab.msdn.microsoft.com/productfeedback/. This is a pretty hefty architectural change request,
and changing the transaction semantics will also affect all the existing applications. To be honest,
I wouldn't have much hope for such a change to happen, but I don't make such call, MS does. Use the
above link to suggest, and the suggestion will go to the right place.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www. solidqualitylearning
.com/
Blog: http:// solidqualitylearning
.com/blogs/tibor/
"Marius Horak" <nobody@eu.con> wrote in message news:Oy9q8cCRGHA.3052@TK2MSFTNGP09.phx.gbl...
> Dear M$,
>
> Can you get rid off Logfile in your next release of SQL Server, please.
> It's pain in neck and 30 year old technology.
>
> MH
| |
| David Portas 2006-03-10, 11:23 am |
| Marius Horak wrote:
>
> Backup/restore/space
Can you elaborate? Why should log cause you a problem with backup and
restore? What space issue do you have? What recovery model are you
running under? If you aren't implementing transaction log backups then
you need to choose Simple Recovery.
>
> Without a logfile.
>
> Technology used by Iterbase.
>
Do you mean InterBase? As far as I understand it InterBase implements
MVCC only so although rollback is supported there is no roll-forward
logging. In a high-volume, high-availability OLTP environment the
exposure to data loss between backups would therefore be unacceptable
to many customers. Googling on this I notice there are third party
vendors who supply add-on products for InterBase to fill this gap. Am I
wrong or out of date? What alternative is there to roll-forward
logging? Please be more specific.
SQL Server 2005 *does* support multi-versioning like InterBase but it
is not and cannot be a substitute for logging.
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--
|
|
|
|
|