Sunday, March 11, 2012
Choosing a Licensing Mode
Services for SQL Server 2K. We wish to install according to the following
scheme,
- Report Server: on our web server (ws1)
- Report Manager: on our web server (ws1)
- Report Server Database: on our SQL Server db (sql1)
- Report Designer: on our workstations
Reading what is on this page
http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/rsdepgd.mspx,
it says that "You must have a valid SQL Server license for each computer
that has a SQL Server 2000 component (such as Reporting Services) installed.
For example, the computer running Reporting Services requires a SQL Server
license. If the report server database is located remotely, a separate
license is required for the remote computer running SQL Server."
Does this mean that we must have a separate SQL Server license for our ws1
machine to be able to run Report Server and Report Manager than the license
we have on our sql1 machine? Thanks in advance :-)The following is general guidance, I'm not an expert on licensing so what I
say definitely does not 'go'. I recommend you speak with your TAM/Sales rep
to ensure you're correctly licensed based on your deployment, hardware, etc.
In general, you need a SQL licence for each computer on which you deploy
server components. Thus, if you deploy report server on computer A and your
SQL engine is on computer B, you need to have a SQL licence for of A and
another for B, totalling 2 processor licenses.
Thyen if you have multi-proc machines, it gets interesting. Speak with
your TAM/Sales rep.
-Lukasz
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"dw" <cougarmana_NOSPAM@.uncw.edu> wrote in message
news:e9KNnVZbEHA.1644@.tk2msftngp13.phx.gbl...
> Hello, all. We have a question as to the licensing mode of Reporting
> Services for SQL Server 2K. We wish to install according to the following
> scheme,
> - Report Server: on our web server (ws1)
> - Report Manager: on our web server (ws1)
> - Report Server Database: on our SQL Server db (sql1)
> - Report Designer: on our workstations
> Reading what is on this page
> http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/rsdepgd.mspx,
> it says that "You must have a valid SQL Server license for each computer
> that has a SQL Server 2000 component (such as Reporting Services)
> installed.
> For example, the computer running Reporting Services requires a SQL Server
> license. If the report server database is located remotely, a separate
> license is required for the remote computer running SQL Server."
> Does this mean that we must have a separate SQL Server license for our ws1
> machine to be able to run Report Server and Report Manager than the
> license
> we have on our sql1 machine? Thanks in advance :-)
>|||Thanks Lukasz. That's what I was afraid of.
"Lukasz Pawlowski [MSFT]" <lukaszp@.online.microsoft.com> wrote in message
news:esiORlcbEHA.2340@.TK2MSFTNGP10.phx.gbl...
> The following is general guidance, I'm not an expert on licensing so what
I
> say definitely does not 'go'. I recommend you speak with your TAM/Sales
rep
> to ensure you're correctly licensed based on your deployment, hardware,
etc.
> In general, you need a SQL licence for each computer on which you deploy
> server components. Thus, if you deploy report server on computer A and
your
> SQL engine is on computer B, you need to have a SQL licence for of A and
> another for B, totalling 2 processor licenses.
> Thyen if you have multi-proc machines, it gets interesting. Speak with
> your TAM/Sales rep.
> -Lukasz
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "dw" <cougarmana_NOSPAM@.uncw.edu> wrote in message
> news:e9KNnVZbEHA.1644@.tk2msftngp13.phx.gbl...
> > Hello, all. We have a question as to the licensing mode of Reporting
> > Services for SQL Server 2K. We wish to install according to the
following
> > scheme,
> >
> > - Report Server: on our web server (ws1)
> > - Report Manager: on our web server (ws1)
> > - Report Server Database: on our SQL Server db (sql1)
> > - Report Designer: on our workstations
> >
> > Reading what is on this page
> >
http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/rsdepgd.mspx,
> > it says that "You must have a valid SQL Server license for each computer
> > that has a SQL Server 2000 component (such as Reporting Services)
> > installed.
> > For example, the computer running Reporting Services requires a SQL
Server
> > license. If the report server database is located remotely, a separate
> > license is required for the remote computer running SQL Server."
> >
> > Does this mean that we must have a separate SQL Server license for our
ws1
> > machine to be able to run Report Server and Report Manager than the
> > license
> > we have on our sql1 machine? Thanks in advance :-)
> >
> >
>
Thursday, March 8, 2012
cheksum function bug
i came accross of the problem with checksum function which we use
intensively for large db searches.
According to manul it should always produce different value for different
string value and unique for the same strings.
Here is an example when different strings produce the same checksum value:
select checksum('AJUBELTKAJUBEL')
select checksum('AJUBSBTKAJUBSB')
select checksum('AJUCGBTKAJUCGB')
--
-2013265910Gene,
Although CHECKSUM should always produce the same value for the same string,
it absolutely does not always produce a different value for different
strings. The Books Online do not promise this, but say, "we do not
recommend using CHECKSUM to detect whether values have changed, unless your
application can tolerate occasionally missing a change."
When you think about it, CHECKSUM returns an integer value, with only
4,294,967,296 possible values. However, a 10-character string using the 10
digits and 26 letters of the alphabet has 3,656,158,440,062,976 possible
values. The likelihood of collision is increased, because the algorithm
uses exclusive-ors in computing the has value.
RLF
"Gene." <Gene@.discussions.microsoft.com> wrote in message
news:61D1F361-C95A-4F5C-B29A-249EFE0412D8@.microsoft.com...
> Hi
> i came accross of the problem with checksum function which we use
> intensively for large db searches.
> According to manul it should always produce different value for different
> string value and unique for the same strings.
> Here is an example when different strings produce the same checksum value:
> select checksum('AJUBELTKAJUBEL')
> select checksum('AJUBSBTKAJUBSB')
> select checksum('AJUCGBTKAJUCGB')
> --
> -2013265910
>|||Thank you Russell again.
I was under impression that different combination of letters should always
produce different integer.
Regards, Gene.
"Russell Fields" wrote:
> Gene,
> Although CHECKSUM should always produce the same value for the same string,
> it absolutely does not always produce a different value for different
> strings. The Books Online do not promise this, but say, "we do not
> recommend using CHECKSUM to detect whether values have changed, unless your
> application can tolerate occasionally missing a change."
> When you think about it, CHECKSUM returns an integer value, with only
> 4,294,967,296 possible values. However, a 10-character string using the 10
> digits and 26 letters of the alphabet has 3,656,158,440,062,976 possible
> values. The likelihood of collision is increased, because the algorithm
> uses exclusive-ors in computing the has value.
> RLF
> "Gene." <Gene@.discussions.microsoft.com> wrote in message
> news:61D1F361-C95A-4F5C-B29A-249EFE0412D8@.microsoft.com...
> > Hi
> >
> > i came accross of the problem with checksum function which we use
> > intensively for large db searches.
> > According to manul it should always produce different value for different
> > string value and unique for the same strings.
> >
> > Here is an example when different strings produce the same checksum value:
> >
> > select checksum('AJUBELTKAJUBEL')
> > select checksum('AJUBSBTKAJUBSB')
> > select checksum('AJUCGBTKAJUCGB')
> > --
> >
> > -2013265910
> >
>
>|||Gene,
Just getting back to you. If you are saving the checkdigit for a string in
a column that is a good way to speed up some searches. In fact, the
CHECKDIGIT was designed as a hash function for just that reason. However,
to make sure you have a hit, you also have to use the actual value. E.g.
DECLARE @.LongString NVARCHAR (255)
SET @.LongString = 'We do not recommend using CHECKSUM to detect whether
values have changed, unless your
application can tolerate occasionally missing a change.'
CREATE TABLE LongStrings
(StringKey INT,
SearchableText NVARCHAR(255),
TextHash INT)
CREATE INDEX TextHash ON LongStrings (TextHash)
INSERT INTO LongStrings VALUES (1, @.LongString, CHECKSUM (@.LongString))
-- And insert many many more rows in real life.
SELECT * FROM LongStrings
WHERE TextHash = CHECKSUM (@.LongString)
AND SearchableText = @.LongString
You will notice that only the hash has an index. This reduces storage for
the LongStrings table since it does not have the big index on
SearchableText, but it does require some extra I/O to compare the
SearchableText for rows where TextHash is equal to the queried value.
RLF
"Gene." <Gene@.discussions.microsoft.com> wrote in message
news:D1BFCA68-84CA-4DFB-8F20-DD70E3C2791D@.microsoft.com...
> Thank you Russell again.
> I was under impression that different combination of letters should always
> produce different integer.
> Regards, Gene.
> "Russell Fields" wrote:
>> Gene,
>> Although CHECKSUM should always produce the same value for the same
>> string,
>> it absolutely does not always produce a different value for different
>> strings. The Books Online do not promise this, but say, "we do not
>> recommend using CHECKSUM to detect whether values have changed, unless
>> your
>> application can tolerate occasionally missing a change."
>> When you think about it, CHECKSUM returns an integer value, with only
>> 4,294,967,296 possible values. However, a 10-character string using the
>> 10
>> digits and 26 letters of the alphabet has 3,656,158,440,062,976 possible
>> values. The likelihood of collision is increased, because the algorithm
>> uses exclusive-ors in computing the has value.
>> RLF
>> "Gene." <Gene@.discussions.microsoft.com> wrote in message
>> news:61D1F361-C95A-4F5C-B29A-249EFE0412D8@.microsoft.com...
>> > Hi
>> >
>> > i came accross of the problem with checksum function which we use
>> > intensively for large db searches.
>> > According to manul it should always produce different value for
>> > different
>> > string value and unique for the same strings.
>> >
>> > Here is an example when different strings produce the same checksum
>> > value:
>> >
>> > select checksum('AJUBELTKAJUBEL')
>> > select checksum('AJUBSBTKAJUBSB')
>> > select checksum('AJUCGBTKAJUCGB')
>> > --
>> >
>> > -2013265910
>> >
>>|||Grrr, I see that I used CHECKDIGIT in the first paragraph. That should be,
of course, CHECKSUM. - RLF
"Russell Fields" <russellfields@.nomail.com> wrote in message
news:%23J0Q6OYEIHA.3980@.TK2MSFTNGP03.phx.gbl...
> Gene,
> Just getting back to you. If you are saving the checkdigit for a string
> in a column that is a good way to speed up some searches. In fact, the
> CHECKDIGIT was designed as a hash function for just that reason. However,
> to make sure you have a hit, you also have to use the actual value. E.g.
> DECLARE @.LongString NVARCHAR (255)
> SET @.LongString = 'We do not recommend using CHECKSUM to detect whether
> values have changed, unless your
> application can tolerate occasionally missing a change.'
> CREATE TABLE LongStrings
> (StringKey INT,
> SearchableText NVARCHAR(255),
> TextHash INT)
> CREATE INDEX TextHash ON LongStrings (TextHash)
> INSERT INTO LongStrings VALUES (1, @.LongString, CHECKSUM (@.LongString))
> -- And insert many many more rows in real life.
> SELECT * FROM LongStrings
> WHERE TextHash = CHECKSUM (@.LongString)
> AND SearchableText = @.LongString
> You will notice that only the hash has an index. This reduces storage for
> the LongStrings table since it does not have the big index on
> SearchableText, but it does require some extra I/O to compare the
> SearchableText for rows where TextHash is equal to the queried value.
>
> RLF
> "Gene." <Gene@.discussions.microsoft.com> wrote in message
> news:D1BFCA68-84CA-4DFB-8F20-DD70E3C2791D@.microsoft.com...
>> Thank you Russell again.
>> I was under impression that different combination of letters should
>> always
>> produce different integer.
>> Regards, Gene.
>> "Russell Fields" wrote:
>> Gene,
>> Although CHECKSUM should always produce the same value for the same
>> string,
>> it absolutely does not always produce a different value for different
>> strings. The Books Online do not promise this, but say, "we do not
>> recommend using CHECKSUM to detect whether values have changed, unless
>> your
>> application can tolerate occasionally missing a change."
>> When you think about it, CHECKSUM returns an integer value, with only
>> 4,294,967,296 possible values. However, a 10-character string using the
>> 10
>> digits and 26 letters of the alphabet has 3,656,158,440,062,976 possible
>> values. The likelihood of collision is increased, because the algorithm
>> uses exclusive-ors in computing the has value.
>> RLF
>> "Gene." <Gene@.discussions.microsoft.com> wrote in message
>> news:61D1F361-C95A-4F5C-B29A-249EFE0412D8@.microsoft.com...
>> > Hi
>> >
>> > i came accross of the problem with checksum function which we use
>> > intensively for large db searches.
>> > According to manul it should always produce different value for
>> > different
>> > string value and unique for the same strings.
>> >
>> > Here is an example when different strings produce the same checksum
>> > value:
>> >
>> > select checksum('AJUBELTKAJUBEL')
>> > select checksum('AJUBSBTKAJUBSB')
>> > select checksum('AJUCGBTKAJUCGB')
>> > --
>> >
>> > -2013265910
>> >
>>
>
Friday, February 24, 2012
checking the existance of fields and types
fields and data types according to requirements
I was looking at the syscolumns table for some of this information but
I've discovered that in my playing (creating and deleting tables) thre
are multiple entries for a field that is in table that is created then
deleted then created again.
Is this a problem? Is there a better way to get at the information ie
the table, field, and type exist in a database?Use the INFORMATION_SCHEMA views. See Books Online for details.
Most metadata can be retrieved more easily from the info schema than
from system tables. There are some exceptions but system tables are
best left alone unless you really have to use them. They will be
supported only for backwards compatibility and won't reflect new
features in future versions.
--
David Portas
SQL Server MVP
--|||William Kossack (kossackw@.njc.org) writes:
> I'm trying to write a program in cold fusion to check the existance of
> fields and data types according to requirements
> I was looking at the syscolumns table for some of this information but
> I've discovered that in my playing (creating and deleting tables) thre
> are multiple entries for a field that is in table that is created then
> deleted then created again.
This sounds very strange. My guess is that you are joining syscolumns
with systypes incorrectly. (Those two tables are indeed a bit tricky
to match up.) Care to post a query that gives funny result?
> Is this a problem? Is there a better way to get at the information ie
> the table, field, and type exist in a database?
Some people tout the INFORMATION_SCHEMA views, but since they only
give a subset of the metadata information, they're pretty useless in
my opinion. They are mainly interesting if you want to write portable
meta-data queries.
There are also functions like object_id, columnproperty which can be
useful at times, but they have the drawback that they are restricted
to the current database.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp