September 25, 2006 at 10:39 am
This'll be my first from-scratch installation of SQL2k. The box will be running Windows Server 2003 Enterprise. Our other SQL2k system was installed outside of our Active Directory Domain for, according to our now-gone sys admin, security reasons. We're now wondering if we should put the new system on our domain or not.
So, what are the pros/cons of doing this?
September 25, 2006 at 11:46 am
It depends on your business needs. If it is a secure system, it may be a reason for putting it outide the domain, but in this case you will not be able to use the advantages of Integrated authentication for Domain users.
We don't know what system you are talking about: for internal users, for outside customers etc.
Regards,Yelena Varsha
September 25, 2006 at 12:30 pm
It'll be a peoplesoft database, serving a separate application server. The 'Bobs' have already informed me that the app will not do integrated authentication. Made my day, I can tell ya...
September 26, 2006 at 3:49 pm
If it is a CRM and uses attachments it may require Integrated for this part. I am running one of the industry-leader CRMs that uses SQL Server authentication but attachments are copied to the server in the security context of the Windows user.
In your case I would ask application vendor Peoplesoft support what do they recommend or require.
Regards,Yelena Varsha
September 26, 2006 at 3:56 pm
That is what we ended up doing, and they did make a strong recommendation. Thanks for your help, Yelena.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply