Re: EnumErrorlogs using SQLDMO

I was hoping it was something to do with the current holder of the ashes (ie
you could have waited about a year for it to fix itself),

but I'm seeing the same here in the UK on totally UK Server. The description
is a bit vague in BOL , going to try a few things.

cheers,
Andy.


"MartinC" <MartinC@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:79DF19A6-89D7-4464-92BF-EC7F6E6B78BB@xxxxxxxxxxxxxxxx
>I am wanting to use the EnumErrorlogs method of the SQLServer object to
> identify which of the error logs have been written to in a specified
> period.
> I also need to be able to deploy this to any of our SQL Servers which
> could
> all be running with different locales.
>
> The Date column in the QueryResults output shows this but not in the date
> format that I expected. My server is set to English(Australian), my
> default
> language for my login in SQL Server is British English ... i.e. everything
> is
> configured to return dates in the D/M/Y format. However, the date
> string
> returned from EnumErrorlogs is in a M/D/Y format which then messes up the
> remainder of my processing.
>
> Is the result ALWAYS returned in M/D/Y ? If so then I could at least
> code
> for that, but if it is possible for it to be in the D/M/Y format then I
> need
> to know where this is set so that I can test for it before continuing to
> process the logs.
>
> Can anyone direct me to information about this?


.

Loading