Hi,
I have Installed MSDE 2000 on Windows 98 SE box After REBOOT MSDE
service is running.
I am not able to connect to the MSDE in WIndows Authentication mode
while using Login ( sa ) / password the connectivity is done.
My GUI uses the MSDE connection in "Windows Authentication Mode" which
is working fine with the 2K/XP but not with 98SE/ME.
The MSDE Readme.txt says that on 98 / ME the default Connectivity mode
is "Windows Authentication" BUT its not working in that way.
I have tried SECURITYMODE=SQL as command line to setup.exe as well but
results are same.
Any clue to run it in WMA Mode on Win98SE/ME ?
thanks
kapil
Hi Kaps,
Win98 doesn't provide the infrastructure that MSDE needs to use Windows
Authentication. You will need to use SQL Server authentication and specify
an password for sa (SAPWD) while installing it.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"kaps" <kapilkj@.gmail.com> wrote in message
news:1103617693.026085.125330@.f14g2000cwb.googlegr oups.com...
> Hi,
> I have Installed MSDE 2000 on Windows 98 SE box After REBOOT MSDE
> service is running.
> I am not able to connect to the MSDE in WIndows Authentication mode
> while using Login ( sa ) / password the connectivity is done.
> My GUI uses the MSDE connection in "Windows Authentication Mode" which
> is working fine with the 2K/XP but not with 98SE/ME.
> The MSDE Readme.txt says that on 98 / ME the default Connectivity mode
> is "Windows Authentication" BUT its not working in that way.
> I have tried SECURITYMODE=SQL as command line to setup.exe as well but
> results are same.
> Any clue to run it in WMA Mode on Win98SE/ME ?
>
> thanks
> kapil
>
Showing posts with label reboot. Show all posts
Showing posts with label reboot. Show all posts
Friday, March 23, 2012
MSDE 2000 installation on Windows 98 SE
Saturday, February 25, 2012
MSDB Recovery Model Option
Hi,
On one of our servers, whenever there is a system reboot the recovery model
option on the MSDB database is reset to 'Simple'. This is causing the
Transaction Log to fail. At that point I have to go back and change it to
'Full' again. Is there any setting/configuration that I can change so the
recovery model is not changed and is always 'Full' like I setup. Any kind of
input on this is very much appreciated.
Thank you
This is by design. Leave the MSDB database in simple recovery and do more
frequent full backups. SQL does not like full recovery for system
databases.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"helpplease" <helpplease@.discussions.microsoft.com> wrote in message
news:C862E63E-B996-43A8-8936-7C691D15C0F0@.microsoft.com...
> Hi,
> On one of our servers, whenever there is a system reboot the recovery
> model
> option on the MSDB database is reset to 'Simple'. This is causing the
> Transaction Log to fail. At that point I have to go back and change it to
> 'Full' again. Is there any setting/configuration that I can change so the
> recovery model is not changed and is always 'Full' like I setup. Any kind
> of
> input on this is very much appreciated.
> Thank you
>
|||Thank you very very much Geoff.
"Geoff N. Hiten" wrote:
> This is by design. Leave the MSDB database in simple recovery and do more
> frequent full backups. SQL does not like full recovery for system
> databases.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "helpplease" <helpplease@.discussions.microsoft.com> wrote in message
> news:C862E63E-B996-43A8-8936-7C691D15C0F0@.microsoft.com...
>
>
On one of our servers, whenever there is a system reboot the recovery model
option on the MSDB database is reset to 'Simple'. This is causing the
Transaction Log to fail. At that point I have to go back and change it to
'Full' again. Is there any setting/configuration that I can change so the
recovery model is not changed and is always 'Full' like I setup. Any kind of
input on this is very much appreciated.
Thank you
This is by design. Leave the MSDB database in simple recovery and do more
frequent full backups. SQL does not like full recovery for system
databases.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"helpplease" <helpplease@.discussions.microsoft.com> wrote in message
news:C862E63E-B996-43A8-8936-7C691D15C0F0@.microsoft.com...
> Hi,
> On one of our servers, whenever there is a system reboot the recovery
> model
> option on the MSDB database is reset to 'Simple'. This is causing the
> Transaction Log to fail. At that point I have to go back and change it to
> 'Full' again. Is there any setting/configuration that I can change so the
> recovery model is not changed and is always 'Full' like I setup. Any kind
> of
> input on this is very much appreciated.
> Thank you
>
|||Thank you very very much Geoff.
"Geoff N. Hiten" wrote:
> This is by design. Leave the MSDB database in simple recovery and do more
> frequent full backups. SQL does not like full recovery for system
> databases.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "helpplease" <helpplease@.discussions.microsoft.com> wrote in message
> news:C862E63E-B996-43A8-8936-7C691D15C0F0@.microsoft.com...
>
>
MSDB Recovery Model Option
Hi,
On one of our servers, whenever there is a system reboot the recovery model
option on the MSDB database is reset to 'Simple'. This is causing the
Transaction Log to fail. At that point I have to go back and change it to
'Full' again. Is there any setting/configuration that I can change so the
recovery model is not changed and is always 'Full' like I setup. Any kind of
input on this is very much appreciated.
Thank youThis is by design. Leave the MSDB database in simple recovery and do more
frequent full backups. SQL does not like full recovery for system
databases.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"helpplease" <helpplease@.discussions.microsoft.com> wrote in message
news:C862E63E-B996-43A8-8936-7C691D15C0F0@.microsoft.com...
> Hi,
> On one of our servers, whenever there is a system reboot the recovery
> model
> option on the MSDB database is reset to 'Simple'. This is causing the
> Transaction Log to fail. At that point I have to go back and change it to
> 'Full' again. Is there any setting/configuration that I can change so the
> recovery model is not changed and is always 'Full' like I setup. Any kind
> of
> input on this is very much appreciated.
> Thank you
>|||Thank you very very much Geoff.
"Geoff N. Hiten" wrote:
> This is by design. Leave the MSDB database in simple recovery and do more
> frequent full backups. SQL does not like full recovery for system
> databases.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "helpplease" <helpplease@.discussions.microsoft.com> wrote in message
> news:C862E63E-B996-43A8-8936-7C691D15C0F0@.microsoft.com...
> > Hi,
> >
> > On one of our servers, whenever there is a system reboot the recovery
> > model
> > option on the MSDB database is reset to 'Simple'. This is causing the
> > Transaction Log to fail. At that point I have to go back and change it to
> > 'Full' again. Is there any setting/configuration that I can change so the
> > recovery model is not changed and is always 'Full' like I setup. Any kind
> > of
> > input on this is very much appreciated.
> >
> > Thank you
> >
>
>
On one of our servers, whenever there is a system reboot the recovery model
option on the MSDB database is reset to 'Simple'. This is causing the
Transaction Log to fail. At that point I have to go back and change it to
'Full' again. Is there any setting/configuration that I can change so the
recovery model is not changed and is always 'Full' like I setup. Any kind of
input on this is very much appreciated.
Thank youThis is by design. Leave the MSDB database in simple recovery and do more
frequent full backups. SQL does not like full recovery for system
databases.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"helpplease" <helpplease@.discussions.microsoft.com> wrote in message
news:C862E63E-B996-43A8-8936-7C691D15C0F0@.microsoft.com...
> Hi,
> On one of our servers, whenever there is a system reboot the recovery
> model
> option on the MSDB database is reset to 'Simple'. This is causing the
> Transaction Log to fail. At that point I have to go back and change it to
> 'Full' again. Is there any setting/configuration that I can change so the
> recovery model is not changed and is always 'Full' like I setup. Any kind
> of
> input on this is very much appreciated.
> Thank you
>|||Thank you very very much Geoff.
"Geoff N. Hiten" wrote:
> This is by design. Leave the MSDB database in simple recovery and do more
> frequent full backups. SQL does not like full recovery for system
> databases.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "helpplease" <helpplease@.discussions.microsoft.com> wrote in message
> news:C862E63E-B996-43A8-8936-7C691D15C0F0@.microsoft.com...
> > Hi,
> >
> > On one of our servers, whenever there is a system reboot the recovery
> > model
> > option on the MSDB database is reset to 'Simple'. This is causing the
> > Transaction Log to fail. At that point I have to go back and change it to
> > 'Full' again. Is there any setting/configuration that I can change so the
> > recovery model is not changed and is always 'Full' like I setup. Any kind
> > of
> > input on this is very much appreciated.
> >
> > Thank you
> >
>
>
MSDB Recovery Model Option
Hi,
On one of our servers, whenever there is a system reboot the recovery model
option on the MSDB database is reset to 'Simple'. This is causing the
Transaction Log to fail. At that point I have to go back and change it to
'Full' again. Is there any setting/configuration that I can change so the
recovery model is not changed and is always 'Full' like I setup. Any kind o
f
input on this is very much appreciated.
Thank youThis is by design. Leave the MSDB database in simple recovery and do more
frequent full backups. SQL does not like full recovery for system
databases.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"helpplease" <helpplease@.discussions.microsoft.com> wrote in message
news:C862E63E-B996-43A8-8936-7C691D15C0F0@.microsoft.com...
> Hi,
> On one of our servers, whenever there is a system reboot the recovery
> model
> option on the MSDB database is reset to 'Simple'. This is causing the
> Transaction Log to fail. At that point I have to go back and change it to
> 'Full' again. Is there any setting/configuration that I can change so the
> recovery model is not changed and is always 'Full' like I setup. Any kind
> of
> input on this is very much appreciated.
> Thank you
>|||Thank you very very much Geoff.
"Geoff N. Hiten" wrote:
> This is by design. Leave the MSDB database in simple recovery and do more
> frequent full backups. SQL does not like full recovery for system
> databases.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "helpplease" <helpplease@.discussions.microsoft.com> wrote in message
> news:C862E63E-B996-43A8-8936-7C691D15C0F0@.microsoft.com...
>
>
On one of our servers, whenever there is a system reboot the recovery model
option on the MSDB database is reset to 'Simple'. This is causing the
Transaction Log to fail. At that point I have to go back and change it to
'Full' again. Is there any setting/configuration that I can change so the
recovery model is not changed and is always 'Full' like I setup. Any kind o
f
input on this is very much appreciated.
Thank youThis is by design. Leave the MSDB database in simple recovery and do more
frequent full backups. SQL does not like full recovery for system
databases.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"helpplease" <helpplease@.discussions.microsoft.com> wrote in message
news:C862E63E-B996-43A8-8936-7C691D15C0F0@.microsoft.com...
> Hi,
> On one of our servers, whenever there is a system reboot the recovery
> model
> option on the MSDB database is reset to 'Simple'. This is causing the
> Transaction Log to fail. At that point I have to go back and change it to
> 'Full' again. Is there any setting/configuration that I can change so the
> recovery model is not changed and is always 'Full' like I setup. Any kind
> of
> input on this is very much appreciated.
> Thank you
>|||Thank you very very much Geoff.
"Geoff N. Hiten" wrote:
> This is by design. Leave the MSDB database in simple recovery and do more
> frequent full backups. SQL does not like full recovery for system
> databases.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "helpplease" <helpplease@.discussions.microsoft.com> wrote in message
> news:C862E63E-B996-43A8-8936-7C691D15C0F0@.microsoft.com...
>
>
Subscribe to:
Posts (Atom)