|
|
Posted by Jason Cumberland on 11/21/06 15:37
As for your port question, we have successfully done this as well.
On Nov 21, 9:34 am, "Jason Cumberland" <jcumberl...@gmail.com> wrote:
> David,
> I've had several 2000 and 2005 SQL instances running on the same
> Windows 2003 server without running into dll conflicts. As far as your
> licensing options I don't think that will be a problem either, just
> something you need to work out with your software vendor.
>
> On Nov 20, 3:57 am, "David" <david.goody...@gmail.com> wrote:
>
> > Hi all,
>
> > I just asked some people to help me out and phone microsoft with the
> > following information, kindly they refused unless we setup a support
> > contract with them first, for pre-sales information. (That really does
> > not sound like good business sense to me - anyway here is our problem,
> > if anyone could help thanks).
>
> > "To tell and ask microsoft:
>
> > We will be setting up a microsoft sql server 2000 instance running on a
> > windows 2003 server.
>
> > 1) We need to check this can run alongside a microsoft 2003 sql server
> > (either workgroup or standard edition), on the same machine. Are there
> > any .dll clashes if we do this? If there are can we run SQL Server
> > 2000, in a virtual machine running windows 2000 professional. (I have a
> > licenced copy we can use for this).
>
> > 2) If we run one instance of 2000, and one of 2003 of the sql servers,
> > can one use the processor licence model, and one use the CAL licence
> > model."
>
> > Thanks for any help, and any idea why they actually force you to use
> > news groups for pre-sales information?
>
> > David
Navigation:
[Reply to this message]
|