Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*SQL\s+Agent\s+Licensing\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*SQL\s+Agent\s+Licensing\s*$/: 3 ]

Total 3 documents matching your query.

1. SQL Agent Licensing (score: 1): Author: Bo Ossinger <ossinger AT WSU DOT EDU>; Date: Tue, 9 Feb 1999 13:54:12 -0800; We've successfully installed the SQL connect agent on one of our NT clients, but in order to configure it correctly we needed to define two separate nodenames on that machine (and to the adsm server; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-02/msg00595.html (10,866 bytes)
2. Re: SQL Agent Licensing (score: 1): Author: Chris Zaremba <zaremba AT US.IBM DOT COM>; Date: Wed, 10 Feb 1999 09:58:22 -0500; Bo, Yes, when using two distinct node names, two client licenses are required on the ADSM server. Chris Zaremba ADSM Agent Development internet zaremba AT us.ibm DOT com; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-02/msg00633.html (10,609 bytes)
3. Re: SQL Agent Licensing (score: 1): Author: Barry Hill <BarryH AT ECHD DOT ORG>; Date: Wed, 10 Feb 1999 11:56:31 -0600; Yes, but is that extra server node license included with the SQL Connect Agent? 400 W 4th Street Odessa, TX 79761 (915) 640-1080 (915) 640-1378 FAX; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-02/msg00644.html (11,300 bytes)

Current List: 1 - 3
Page: [1]