Showing posts with label engine. Show all posts
Showing posts with label engine. Show all posts

Wednesday, March 7, 2012

CPU or Client Version

We will use are SQL server as a search engine for are clients docs and online
jobtracking for are websites.
If you are asking what licensing model to use, you will probably have to use
per processor. I base that recommendation on the fact that you mention that
youe clients are accessing SQL Server through your websites.
Keith Kratochvil
"George" <George@.discussions.microsoft.com> wrote in message
news:B37091AA-C4D4-48A9-8270-6FBDCCA815F2@.microsoft.com...
> We will use are SQL server as a search engine for are clients docs and
> online
> jobtracking for are websites.

CPU or Client Version

We will use are SQL server as a search engine for are clients docs and onlin
e
jobtracking for are websites.If you are asking what licensing model to use, you will probably have to use
per processor. I base that recommendation on the fact that you mention that
youe clients are accessing SQL Server through your websites.
Keith Kratochvil
"George" <George@.discussions.microsoft.com> wrote in message
news:B37091AA-C4D4-48A9-8270-6FBDCCA815F2@.microsoft.com...
> We will use are SQL server as a search engine for are clients docs and
> online
> jobtracking for are websites.

CPU or Client Version

We will use are SQL server as a search engine for are clients docs and online
jobtracking for are websites.If you are asking what licensing model to use, you will probably have to use
per processor. I base that recommendation on the fact that you mention that
youe clients are accessing SQL Server through your websites.
--
Keith Kratochvil
"George" <George@.discussions.microsoft.com> wrote in message
news:B37091AA-C4D4-48A9-8270-6FBDCCA815F2@.microsoft.com...
> We will use are SQL server as a search engine for are clients docs and
> online
> jobtracking for are websites.