Log in problem

I am using SQL 2000 developer edition and all has been
working fine, until today. In Entrprise manager I can
not log into my local database however I can log into a
remote one. Additionally my local development
applications can access data and function fine they all
use SQL server authentaction.
In enterprise manager whenI try to log in I get the
following message-
Log In Filed for user "name"
please verify your SQL Server is running and check ....
I am sure you all get the idea.
I have tried everything and changed nothing, particularly
any passwords.
Any ideas?
Don
Open Enterprise Manager and right click on the server node.
Select Edit SQL Server Registration Properties. From here,
make sure to enter the correct SQL login and password.
You may also just be experiencing a login time...it's hard
to say without the exact error message. If this is the case,
in Enterprise Manager go to the menu to tools...options. On
the Advanced tab, increase the login timeout from the
default 4 secs to something higher...try 15 to start with.
-Sue
On Mon, 2 Aug 2004 11:54:07 -0700, "Don" <dstull1@.msn.com>
wrote:

>I am using SQL 2000 developer edition and all has been
>working fine, until today. In Entrprise manager I can
>not log into my local database however I can log into a
>remote one. Additionally my local development
>applications can access data and function fine they all
>use SQL server authentaction.
>In enterprise manager whenI try to log in I get the
>following message-
>Log In Filed for user "name"
>please verify your SQL Server is running and check ....
>I am sure you all get the idea.
>I have tried everything and changed nothing, particularly
>any passwords.
>Any ideas?
>Don

Log getting too big

Hello,

I have a local database that is refreshed overnight. A DTS batch grab several views from another database and makes local copy locally. This process creates a hige amount of unnecessary lines in the log file and sometimes so much that the entire available disk space is used, thus crashing the DTS batch. This database is mainly static and non transactional. I wonder if its possible to disable alltogether the logging process for that particular db but I know its part of SQL server so it can't be that simple.

If I limit the size of the log file it gets cluttered and the same problem that if disk space was all used occurs... what should I do ?Not possible to skip the log
But possible to clean it (via backup, or via sp_dboption YourDB, trunc, true, ...)|||You can set the recovery model of the database to simple|||Originally posted by Enigma
You can set the recovery model of the database to simple

... and keep DTS transactions as short as possible - every checkpoint will clean up the transaction log.|||Model recovery already set to simple...

added a SQL task at the end of my batch that does this :

backup log someDatabase with truncate_only;
dbcc shrinkfile (someDatabase_log);

but still my log is several gigabytes big ... maybe Ill add that SQL task after each import tasks...

*sigh*|||Simple-recovery model logs each transaction and clears the log at each CHECKPOINT that's why during ur DTS it gets too big. Try the Bulk-Log recovery model, for it just skips BCPs and SELECT INTO etc. During ur DTS the log may fill-up less than the Simple-Recovery Model. Bulk-Log requires Transaction-Log backups to clear older records.|||I'll give a try at your clever solution... makes sense to me... Ill post a follow up monday if everything went ok (or not). For the past 4 weeks my batch systematically crashed on week-ends.

Thank you all for your time and patience!

Have a good w-e (6pm in europe already...)|||Anyone want to scream bcp?

LOG

Please help.
I received the mnessage below in my SQL server Agent
Error log file.
[LOG] Unable to read local eventlog (reason: The data
area passed to a system call is too small)
I run SQL 2k, SP3, on WIN (adnvanced)2k,SP3.
Please advice or help?.This should help :-
http://support.microsoft.com/?id=811484
--
HTH
Ryan Waight, MCDBA, MCSE
"Olutimi" <olutimi@.hotmail.com> wrote in message
news:3e7e01c37c2e$c79f1fa0$a501280a@.phx.gbl...
> Please help.
> I received the mnessage below in my SQL server Agent
> Error log file.
> [LOG] Unable to read local eventlog (reason: The data
> area passed to a system call is too small)
> I run SQL 2k, SP3, on WIN (adnvanced)2k,SP3.
> Please advice or help?.
>|||This happens when the eventlog service empties then eventlog (which is done regularly). Nothing to
worry about, IMO.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Olutimi" <olutimi@.hotmail.com> wrote in message news:3e7e01c37c2e$c79f1fa0$a501280a@.phx.gbl...
> Please help.
> I received the mnessage below in my SQL server Agent
> Error log file.
> [LOG] Unable to read local eventlog (reason: The data
> area passed to a system call is too small)
> I run SQL 2k, SP3, on WIN (adnvanced)2k,SP3.
> Please advice or help?.
>

Log

When analysing my SQLAGENT.OUT FILE i get this error:
Unable to read local eventlog (reason: The handle is
invalid)
Anyone know what it is?Hi Nefasha,
This "Invalid Handle" error may occur when another process (could be third
party application) is trying to access the handle the same time that the
SQL Server Agent is trying to access the Event Log handler.
Sincerely,
Yih-Yoon Lee [Microsoft]
Microsoft SQL Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.