Outlook licensing on SQL Server

Hi
Just a quick question, if I use outlook as the MAPI client for the SQL
server agent and SQL Mail section of SQL Server 2000 do I need to purchase a
license for the copy of Outlook I will use on the server even though we wll
not actually be using Outlook on that server as a full client?
I forgot to ask if it also means that we need a, Exhange CAL for the SQL
server as Outlook will be communicating with our Exchange server
"OGTI" wrote:

> Hi
> Just a quick question, if I use outlook as the MAPI client for the SQL
> server agent and SQL Mail section of SQL Server 2000 do I need to purchase a
> license for the copy of Outlook I will use on the server even though we wll
> not actually be using Outlook on that server as a full client?
|||Hi.
You need the appropriate Office license and an Exchange CAL.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"OGTI" <OGTI@.discussions.microsoft.com> wrote in message
news:66B8929F-3E51-4CBD-8707-D03834C372DE@.microsoft.com...[vbcol=seagreen]
>I forgot to ask if it also means that we need a, Exhange CAL for the SQL
> server as Outlook will be communicating with our Exchange server
> "OGTI" wrote:

Outlook licensing on SQL Server

Hi
Just a quick question, if I use outlook as the MAPI client for the SQL
server agent and SQL Mail section of SQL Server 2000 do I need to purchase a
license for the copy of Outlook I will use on the server even though we wll
not actually be using Outlook on that server as a full client?I forgot to ask if it also means that we need a, Exhange CAL for the SQL
server as Outlook will be communicating with our Exchange server
"OGTI" wrote:

> Hi
> Just a quick question, if I use outlook as the MAPI client for the SQL
> server agent and SQL Mail section of SQL Server 2000 do I need to purchase
a
> license for the copy of Outlook I will use on the server even though we wl
l
> not actually be using Outlook on that server as a full client?|||Hi.
You need the appropriate Office license and an Exchange CAL.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"OGTI" <OGTI@.discussions.microsoft.com> wrote in message
news:66B8929F-3E51-4CBD-8707-D03834C372DE@.microsoft.com...[vbcol=seagreen]
>I forgot to ask if it also means that we need a, Exhange CAL for the SQL
> server as Outlook will be communicating with our Exchange server
> "OGTI" wrote:
>

OSql util in Sql server 2005

There is support in Osql util in SqlServer 2005 ?

Dear orent,

We now have the sqlcmd utility which is an improvement over the osql utility found in Sql 2000. Osql has been deprecated. Just in case if you are interested, isql has been removed in this version.

http://msdn2.microsoft.com/en-us/library/ms170207.aspx

So to sum it up, osql can still be used in sql 2005 but its certainly better to now use sqlcmd.

HTH,
Suprotim Agarwal

--
http://www.dotnetcurry.com
--

OSQL question

Hi I am trying to write a batch file that will give me all records relating to the query.

osql -S sqlserver -d database -U sa -P "" -Q "select docloc from mhgroup.docmaster where docloc like '%1054193%'"

The query is truncating the 1054193 to 054193....

Is there a problem with using LIKE and the % wildcard in an OSQL statement?

Thanks,
Darrin Carterhow do you know it's truncating? did you see it in profiler? i just ran it here (slightly modified) and it runs correctly, profiler shows the exact string.|||Originally posted by ms_sql_dba
how do you know it's truncating? did you see it in profiler? i just ran it here (slightly modified) and it runs correctly, profiler shows the exact string.

I run it from the batch file that I created. In the DOS window it is missing the 1 at the beginning as well as the % signs

This is the actual statement:

osql -S sqlserver -d database -U sa -P "" -Q "select docloc from mhgroup.docmaster where docloc like '%1054193%'"

This is how it shows up in the DOS window.

I:\>osql -S sqlserver -d database -U sa -P "" -I -Q "select docloc from mhgroup.docmaster where docloc like 054193"|||ok, now I get it. %1 is a replacement for the first argument following the batch file name, which is the reason why %1 disappears. I am not sure about the other % sign.|||you probably will have to use DOS escape codes to make %' visible to OSQL.|||Just use two percent signs (eg : %%) to make one visible to DOS

eg your actual statement should be :

osql -S sqlserver -d database -U sa -P "" -Q "select docloc from mhgroup.docmaster where docloc like '%%1054193%%'"|||Originally posted by Enigma
Just use two percent signs (eg : %%) to make one visible to DOS

eg your actual statement should be :

osql -S sqlserver -d database -U sa -P "" -Q "select docloc from mhgroup.docmaster where docloc like '%%1054193%%'"

That did it. Thanks!