Is there a limit of 256 on CHAR data?

We are creating some VIEWS that concatenate columns for output to FIXED
LENGTH TEXT FILES - with FIXED LENGTH columns.
This is being done for various transmissions - W2 files to the SS Admin,
1099 files to the IRS, eligibility files to various health organizations.
While testing today, in Query Analyzer, it appeared that saying something
like:
Cast( Cast(col1 as char(10))+Cast(Col2 as char(15))...+Cast(Colnn as
char(10)) as char(280))
The 280 was not liked. In QA we could only see a single column of I'm
thinking around 256 bytes?
Does QA have a max size for column display in the grid?
QA->Menu-> Tools.. Options...Results tab. Maximum Characters per column
box. Adjust as necessary.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Steve Z" <szlamany@.antarescomputing_no_spam.com> wrote in message
news:Om8MaQROEHA.2468@.TK2MSFTNGP11.phx.gbl...
> We are creating some VIEWS that concatenate columns for output to FIXED
> LENGTH TEXT FILES - with FIXED LENGTH columns.
> This is being done for various transmissions - W2 files to the SS Admin,
> 1099 files to the IRS, eligibility files to various health organizations.
> While testing today, in Query Analyzer, it appeared that saying something
> like:
> Cast( Cast(col1 as char(10))+Cast(Col2 as char(15))...+Cast(Colnn as
> char(10)) as char(280))
> The 280 was not liked. In QA we could only see a single column of I'm
> thinking around 256 bytes?
> Does QA have a max size for column display in the grid?
>
|||Steve,
Change the max number in Query analyzer 'tools' menu |options|'results' tab.
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"Steve Z" <szlamany@.antarescomputing_no_spam.com> wrote in message
news:Om8MaQROEHA.2468@.TK2MSFTNGP11.phx.gbl...
> We are creating some VIEWS that concatenate columns for output to FIXED
> LENGTH TEXT FILES - with FIXED LENGTH columns.
> This is being done for various transmissions - W2 files to the SS Admin,
> 1099 files to the IRS, eligibility files to various health organizations.
> While testing today, in Query Analyzer, it appeared that saying something
> like:
> Cast( Cast(col1 as char(10))+Cast(Col2 as char(15))...+Cast(Colnn as
> char(10)) as char(280))
> The 280 was not liked. In QA we could only see a single column of I'm
> thinking around 256 bytes?
> Does QA have a max size for column display in the grid?
>
|||> The 280 was not liked. In QA we could only see a single column of I'm
> thinking around 256 bytes?
http://www.aspfaq.com/2272
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
|||Thank you all very much - I was thinking I was crazy...
It worked like a charm.
"Dinesh T.K" <tkdinesh@.nospam.mail.tkdinesh.com> wrote in message
news:e8QpGWROEHA.2704@.TK2MSFTNGP10.phx.gbl...
> Steve,
> Change the max number in Query analyzer 'tools' menu |options|'results'
tab.[vbcol=seagreen]
> --
> Dinesh
> SQL Server MVP
> --
> --
> SQL Server FAQ at
> http://www.tkdinesh.com
> "Steve Z" <szlamany@.antarescomputing_no_spam.com> wrote in message
> news:Om8MaQROEHA.2468@.TK2MSFTNGP11.phx.gbl...
organizations.[vbcol=seagreen]
something
>

Is there a limit of 256 on CHAR data?

We are creating some VIEWS that concatenate columns for output to FIXED
LENGTH TEXT FILES - with FIXED LENGTH columns.
This is being done for various transmissions - W2 files to the SS Admin,
1099 files to the IRS, eligibility files to various health organizations.
While testing today, in Query Analyzer, it appeared that saying something
like:
Cast( Cast(col1 as char(10))+Cast(Col2 as char(15))...+Cast(Colnn as
char(10)) as char(280))
The 280 was not liked. In QA we could only see a single column of I'm
thinking around 256 bytes?
Does QA have a max size for column display in the grid?QA->Menu-> Tools.. Options...Results tab. Maximum Characters per column
box. Adjust as necessary.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Steve Z" <szlamany@.antarescomputing_no_spam.com> wrote in message
news:Om8MaQROEHA.2468@.TK2MSFTNGP11.phx.gbl...
> We are creating some VIEWS that concatenate columns for output to FIXED
> LENGTH TEXT FILES - with FIXED LENGTH columns.
> This is being done for various transmissions - W2 files to the SS Admin,
> 1099 files to the IRS, eligibility files to various health organizations.
> While testing today, in Query Analyzer, it appeared that saying something
> like:
> Cast( Cast(col1 as char(10))+Cast(Col2 as char(15))...+Cast(Colnn as
> char(10)) as char(280))
> The 280 was not liked. In QA we could only see a single column of I'm
> thinking around 256 bytes?
> Does QA have a max size for column display in the grid?
>|||Steve,
Change the max number in Query analyzer 'tools' menu |options|'results' tab.
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Steve Z" <szlamany@.antarescomputing_no_spam.com> wrote in message
news:Om8MaQROEHA.2468@.TK2MSFTNGP11.phx.gbl...
> We are creating some VIEWS that concatenate columns for output to FIXED
> LENGTH TEXT FILES - with FIXED LENGTH columns.
> This is being done for various transmissions - W2 files to the SS Admin,
> 1099 files to the IRS, eligibility files to various health organizations.
> While testing today, in Query Analyzer, it appeared that saying something
> like:
> Cast( Cast(col1 as char(10))+Cast(Col2 as char(15))...+Cast(Colnn as
> char(10)) as char(280))
> The 280 was not liked. In QA we could only see a single column of I'm
> thinking around 256 bytes?
> Does QA have a max size for column display in the grid?
>|||> The 280 was not liked. In QA we could only see a single column of I'm
> thinking around 256 bytes?
http://www.aspfaq.com/2272
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/|||Thank you all very much - I was thinking I was crazy...
It worked like a charm.
"Dinesh T.K" <tkdinesh@.nospam.mail.tkdinesh.com> wrote in message
news:e8QpGWROEHA.2704@.TK2MSFTNGP10.phx.gbl...
> Steve,
> Change the max number in Query analyzer 'tools' menu |options|'results'
tab.
> --
> Dinesh
> SQL Server MVP
> --
> --
> SQL Server FAQ at
> http://www.tkdinesh.com
> "Steve Z" <szlamany@.antarescomputing_no_spam.com> wrote in message
> news:Om8MaQROEHA.2468@.TK2MSFTNGP11.phx.gbl...
organizations.[vbcol=seagreen]
something[vbcol=seagreen]
>sql

Is there a limit of 256 on CHAR data?

We are creating some VIEWS that concatenate columns for output to FIXED
LENGTH TEXT FILES - with FIXED LENGTH columns.
This is being done for various transmissions - W2 files to the SS Admin,
1099 files to the IRS, eligibility files to various health organizations.
While testing today, in Query Analyzer, it appeared that saying something
like:
Cast( Cast(col1 as char(10))+Cast(Col2 as char(15))...+Cast(Colnn as
char(10)) as char(280))
The 280 was not liked. In QA we could only see a single column of I'm
thinking around 256 bytes?
Does QA have a max size for column display in the grid?QA->Menu-> Tools.. Options...Results tab. Maximum Characters per column
box. Adjust as necessary.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Steve Z" <szlamany@.antarescomputing_no_spam.com> wrote in message
news:Om8MaQROEHA.2468@.TK2MSFTNGP11.phx.gbl...
> We are creating some VIEWS that concatenate columns for output to FIXED
> LENGTH TEXT FILES - with FIXED LENGTH columns.
> This is being done for various transmissions - W2 files to the SS Admin,
> 1099 files to the IRS, eligibility files to various health organizations.
> While testing today, in Query Analyzer, it appeared that saying something
> like:
> Cast( Cast(col1 as char(10))+Cast(Col2 as char(15))...+Cast(Colnn as
> char(10)) as char(280))
> The 280 was not liked. In QA we could only see a single column of I'm
> thinking around 256 bytes?
> Does QA have a max size for column display in the grid?
>|||Steve,
Change the max number in Query analyzer 'tools' menu |options|'results' tab.
--
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Steve Z" <szlamany@.antarescomputing_no_spam.com> wrote in message
news:Om8MaQROEHA.2468@.TK2MSFTNGP11.phx.gbl...
> We are creating some VIEWS that concatenate columns for output to FIXED
> LENGTH TEXT FILES - with FIXED LENGTH columns.
> This is being done for various transmissions - W2 files to the SS Admin,
> 1099 files to the IRS, eligibility files to various health organizations.
> While testing today, in Query Analyzer, it appeared that saying something
> like:
> Cast( Cast(col1 as char(10))+Cast(Col2 as char(15))...+Cast(Colnn as
> char(10)) as char(280))
> The 280 was not liked. In QA we could only see a single column of I'm
> thinking around 256 bytes?
> Does QA have a max size for column display in the grid?
>|||> The 280 was not liked. In QA we could only see a single column of I'm
> thinking around 256 bytes?
http://www.aspfaq.com/2272
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/|||Thank you all very much - I was thinking I was crazy...
It worked like a charm.
"Dinesh T.K" <tkdinesh@.nospam.mail.tkdinesh.com> wrote in message
news:e8QpGWROEHA.2704@.TK2MSFTNGP10.phx.gbl...
> Steve,
> Change the max number in Query analyzer 'tools' menu |options|'results'
tab.
> --
> Dinesh
> SQL Server MVP
> --
> --
> SQL Server FAQ at
> http://www.tkdinesh.com
> "Steve Z" <szlamany@.antarescomputing_no_spam.com> wrote in message
> news:Om8MaQROEHA.2468@.TK2MSFTNGP11.phx.gbl...
> > We are creating some VIEWS that concatenate columns for output to FIXED
> > LENGTH TEXT FILES - with FIXED LENGTH columns.
> >
> > This is being done for various transmissions - W2 files to the SS Admin,
> > 1099 files to the IRS, eligibility files to various health
organizations.
> >
> > While testing today, in Query Analyzer, it appeared that saying
something
> > like:
> >
> > Cast( Cast(col1 as char(10))+Cast(Col2 as char(15))...+Cast(Colnn as
> > char(10)) as char(280))
> >
> > The 280 was not liked. In QA we could only see a single column of I'm
> > thinking around 256 bytes?
> >
> > Does QA have a max size for column display in the grid?
> >
> >
>

Is there a doc listing the limitations of Replication under 2005?

I am looking for a doc (BOL, etc.) which enumerates things like limits on the number of columns which can be replicated, or limits on the size of the row. BOL covers this for 2000, but I can not find it in BOL 2005.

Thanks.

Please see the following topic "Maximum Capacity Specifications for SQL Server 2005" in BOL: http://msdn2.microsoft.com/en-us/library/ms143432.aspx

Peng

Is there a bug with Views and Select *?

Hi,
I added some new columns to a table and they do not show up in a View that
references the table "*" selector. If I go into Enterprise Manager and
re-save the view they show up. Has anyone else experienced this problem?
The syntax for the view is :
Select Table1.itemID, Table1.Value, Table2.* where
Table1.ItemID=Table2.ItemID
The new columns are in Table2.
Thanks,
Jerry
Hi,
This is not a bug, this is by design.
If you create a view and then modify the underlying table, the view
definition is not automatically updated. How will a view know if the changes
are also meant for the view definition? Your view could potentially have less
columns than the base table.
If you change the underlying tables, its always best to make sure that your
view's definition is not effected. If it is, you must re-create the view.
Actually, you are re-saving the view definition when you are re-saving the
view.
hth
DeeJay
"JerryK" wrote:

> Hi,
> I added some new columns to a table and they do not show up in a View that
> references the table "*" selector. If I go into Enterprise Manager and
> re-save the view they show up. Has anyone else experienced this problem?
> The syntax for the view is :
> Select Table1.itemID, Table1.Value, Table2.* where
> Table1.ItemID=Table2.ItemID
> The new columns are in Table2.
> Thanks,
> Jerry
>
>
>
|||Jerry,
When a view is created, the name of the view is stored in the sysobjects
table. Information about the columns defined in a view is added to the
syscolumns table, and information about the view dependencies is added to
the sysdepends table. In addition, the text of the CREATE VIEW statement is
added to the syscomments table.
So, when you added the column to the Table2, information in syscolumns for
the view has not been changed. That's why you need to "recompile" (reapply)
the view. The same happens when you drop the column from the Table2. Any
reference to the view produces an error until you reapply the view.
Thanks
Oleg
Message posted via http://www.sqlmonster.com
|||> I added some new columns to a table and they do not show up in a View that
> references the table "*" selector.
Why are you using SELECT *?

> Has anyone else experienced this problem?
It's not a problem, per se; it's actually documented.
You can get around this by actually naming your columns, or using WITH
SCHEMABINDING when you create the view. The former keeps views consistent
with interfaces to them until you have time to attend to both; the latter
forces you to recognize all of the views you will need to change when
considering a change to a base table.
In the meantime, you can issue sp_refreshview 'viewname' instead of using
Enterprise Mangler...
Please post DDL, sample data and desired results.
See http://www.aspfaq.com/5006 for info.

Is there a bug with Views and Select *?

Hi,
I added some new columns to a table and they do not show up in a View that
references the table "*" selector. If I go into Enterprise Manager and
re-save the view they show up. Has anyone else experienced this problem?
The syntax for the view is :
Select Table1.itemID, Table1.Value, Table2.* where
Table1.ItemID=Table2.ItemID
The new columns are in Table2.
Thanks,
JerryHi,
This is not a bug, this is by design.
If you create a view and then modify the underlying table, the view
definition is not automatically updated. How will a view know if the changes
are also meant for the view definition? Your view could potentially have les
s
columns than the base table.
If you change the underlying tables, its always best to make sure that your
view's definition is not effected. If it is, you must re-create the view.
Actually, you are re-saving the view definition when you are re-saving the
view.
hth
DeeJay
"JerryK" wrote:

> Hi,
> I added some new columns to a table and they do not show up in a View that
> references the table "*" selector. If I go into Enterprise Manager and
> re-save the view they show up. Has anyone else experienced this problem?
> The syntax for the view is :
> Select Table1.itemID, Table1.Value, Table2.* where
> Table1.ItemID=Table2.ItemID
> The new columns are in Table2.
> Thanks,
> Jerry
>
>
>|||Jerry,
When a view is created, the name of the view is stored in the sysobjects
table. Information about the columns defined in a view is added to the
syscolumns table, and information about the view dependencies is added to
the sysdepends table. In addition, the text of the CREATE VIEW statement is
added to the syscomments table.
So, when you added the column to the Table2, information in syscolumns for
the view has not been changed. That's why you need to "recompile" (reapply)
the view. The same happens when you drop the column from the Table2. Any
reference to the view produces an error until you reapply the view.
Thanks
Oleg
Message posted via http://www.droptable.com|||> I added some new columns to a table and they do not show up in a View that
> references the table "*" selector.
Why are you using SELECT *?

> Has anyone else experienced this problem?
It's not a problem, per se; it's actually documented.
You can get around this by actually naming your columns, or using WITH
SCHEMABINDING when you create the view. The former keeps views consistent
with interfaces to them until you have time to attend to both; the latter
forces you to recognize all of the views you will need to change when
considering a change to a base table.
In the meantime, you can issue sp_refreshview 'viewname' instead of using
Enterprise Mangler...
Please post DDL, sample data and desired results.
See http://www.aspfaq.com/5006 for info.sql

Is there a bug with Views and Select *?

Hi,
I added some new columns to a table and they do not show up in a View that
references the table "*" selector. If I go into Enterprise Manager and
re-save the view they show up. Has anyone else experienced this problem?
The syntax for the view is :
Select Table1.itemID, Table1.Value, Table2.* where
Table1.ItemID=Table2.ItemID
The new columns are in Table2.
Thanks,
JerryJerry,
When a view is created, the name of the view is stored in the sysobjects
table. Information about the columns defined in a view is added to the
syscolumns table, and information about the view dependencies is added to
the sysdepends table. In addition, the text of the CREATE VIEW statement is
added to the syscomments table.
So, when you added the column to the Table2, information in syscolumns for
the view has not been changed. That's why you need to "recompile" (reapply)
the view. The same happens when you drop the column from the Table2. Any
reference to the view produces an error until you reapply the view.
Thanks
Oleg
--
Message posted via http://www.sqlmonster.com|||Hi,
This is not a bug, this is by design.
If you create a view and then modify the underlying table, the view
definition is not automatically updated. How will a view know if the changes
are also meant for the view definition? Your view could potentially have less
columns than the base table.
If you change the underlying tables, its always best to make sure that your
view's definition is not effected. If it is, you must re-create the view.
Actually, you are re-saving the view definition when you are re-saving the
view.
hth
DeeJay
"JerryK" wrote:
> Hi,
> I added some new columns to a table and they do not show up in a View that
> references the table "*" selector. If I go into Enterprise Manager and
> re-save the view they show up. Has anyone else experienced this problem?
> The syntax for the view is :
> Select Table1.itemID, Table1.Value, Table2.* where
> Table1.ItemID=Table2.ItemID
> The new columns are in Table2.
> Thanks,
> Jerry
>
>
>|||> I added some new columns to a table and they do not show up in a View that
> references the table "*" selector.
Why are you using SELECT *?
> Has anyone else experienced this problem?
It's not a problem, per se; it's actually documented.
You can get around this by actually naming your columns, or using WITH
SCHEMABINDING when you create the view. The former keeps views consistent
with interfaces to them until you have time to attend to both; the latter
forces you to recognize all of the views you will need to change when
considering a change to a base table.
In the meantime, you can issue sp_refreshview 'viewname' instead of using
Enterprise Mangler...
--
Please post DDL, sample data and desired results.
See http://www.aspfaq.com/5006 for info.

is that possible to prevent modifying the name of an IDTSInputColumn90?

Hi,

I'm building a custom SSIS data flow component and I create myself input and output columns from a custom property of my pipeline component. That's why I don't want the user to modify the name of the input and output columns by using the advanced editor.

Is there a way either to make input/output column properties - at least the name - readonly or to override any PipelineComponent method to throw an exception like we do when we want to prevent the user from adding/removing input/output colulmns with methods like PipelineComponent.DeleteOutputColumn?

Thanks for your help,

David

Have you tried SetInputColumnProperty? The name is a property, but I have vague recollection that you cannot use that method to set the name, and end up having to do it on the IDTSInputColumn90 reference directly.

Can you detect a change, and pick this up in Validate? If you can detect a change you could return VS_NEEDSNEWMETADATA, and then correct the problem in ReinitializeMetaData. Not as proactive as preventing a change, but maybe it is better than nothing?

|||

I've tried SetInputColumnProperty but it is called only for custom properties...and the name is not a custom property.

I any case, like you said, when the user modifies the name of an input column, Validate is called and I can detect the error...

Thanks

IS NULL bug(?)

Hello,
My problem is; weird results with a IS NULL clause in a query.
I have a sql2000 dbase, table, 2 columns and the following query:
dt_column = type: datetime
computed: no
length:8
nullable: no
TrimTrailingBlanks:n/a
FixedLenNullnSource:n/a
Collation: null
vc_column = type:varchar
computed: no
length:15
nullable: yes
TrimTrailingBlanks:no
FixedLenNullnSource: no
Collation: SQL_Latin1_General_CP1_CI_AS
q1: select dt_column,vc_colomn from mytable where vc_column is null
->result; >20.000 records where vc_column indeed is null
but, if i expand the query with a date clause like so:
q2: select dt_column,vc_column from mytable where vc_column is null and
year(dt_column) = '2006'
->result; <20.000 records where SOME of the results DO have a value for
the vc_column!
This is strange isnt it ?
I already have a solution to overcome this; but I do not see why i have
to do this:
When I cast the vc_column to a varchar like so:
q3: select dt_column,vc_column from mytable where cast(vc_column as
varchar) and year(dt_column) ='2006'
->the result is good! only null values for the vc_column !
but why do i have to cast a varchar column to a varchar before the is
null will work '?
Thanks very much,
JeroenThis sounds a bit familiar. I ran into a similar problem where unexpected
results were returned from a query (that was a bit more complex than the one
you posted).
What version of SQL Server 2000 are you running?
execute this within Query Analyzer:
SELECT @.@.version
and compare the results to the build list here:
http://www.aspfaq.com/sql2000Builds.asp
In our case we experienced the error on SP4 (SP3 worked fine). Applying the
.2187 hotfix solved our problem. Do you have a test system that you can use
to reproduce the probem and test various patches to see if they solve your
problem?
Keith Kratochvil
"Shuwi" <jeroen.schoenmakers@.gmail.com> wrote in message
news:1160054422.157730.217980@.c28g2000cwb.googlegroups.com...
> Hello,
> My problem is; weird results with a IS NULL clause in a query.
> I have a sql2000 dbase, table, 2 columns and the following query:
> dt_column => type: datetime
> computed: no
> length:8
> nullable: no
> TrimTrailingBlanks:n/a
> FixedLenNullnSource:n/a
> Collation: null
> vc_column => type:varchar
> computed: no
> length:15
> nullable: yes
> TrimTrailingBlanks:no
> FixedLenNullnSource: no
> Collation: SQL_Latin1_General_CP1_CI_AS
> q1: select dt_column,vc_colomn from mytable where vc_column is null
> ->result; >20.000 records where vc_column indeed is null
> but, if i expand the query with a date clause like so:
> q2: select dt_column,vc_column from mytable where vc_column is null and
> year(dt_column) = '2006'
> ->result; <20.000 records where SOME of the results DO have a value for
> the vc_column!
> This is strange isnt it ?
> I already have a solution to overcome this; but I do not see why i have
> to do this:
> When I cast the vc_column to a varchar like so:
> q3: select dt_column,vc_column from mytable where cast(vc_column as
> varchar) and year(dt_column) ='2006'
> ->the result is good! only null values for the vc_column !
> but why do i have to cast a varchar column to a varchar before the is
> null will work '?
> Thanks very much,
> Jeroen
>|||Hi Keith,
Thanks for the quick reply;
The version of sql server is:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002
14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Enterprise
Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
on the > http://www.aspfaq.com/sql2000Builds.asp website I can see no
hotfixes available for this release...?
(seems to stop at build 2187)...
Maybe the 2187 hotfix works here to; I'll test; thanks again.
Jeroen
Keith Kratochvil wrote:
> This sounds a bit familiar. I ran into a similar problem where unexpected
> results were returned from a query (that was a bit more complex than the one
> you posted).
> What version of SQL Server 2000 are you running?
> execute this within Query Analyzer:
> SELECT @.@.version
> and compare the results to the build list here:
> http://www.aspfaq.com/sql2000Builds.asp
> In our case we experienced the error on SP4 (SP3 worked fine). Applying the
> .2187 hotfix solved our problem. Do you have a test system that you can use
> to reproduce the probem and test various patches to see if they solve your
> problem?
>
> --
> Keith Kratochvil
>
> "Shuwi" <jeroen.schoenmakers@.gmail.com> wrote in message
> news:1160054422.157730.217980@.c28g2000cwb.googlegroups.com...
> > Hello,
> >
> > My problem is; weird results with a IS NULL clause in a query.
> >
> > I have a sql2000 dbase, table, 2 columns and the following query:
> > dt_column => > type: datetime
> > computed: no
> > length:8
> > nullable: no
> > TrimTrailingBlanks:n/a
> > FixedLenNullnSource:n/a
> > Collation: null
> >
> > vc_column => > type:varchar
> > computed: no
> > length:15
> > nullable: yes
> > TrimTrailingBlanks:no
> > FixedLenNullnSource: no
> > Collation: SQL_Latin1_General_CP1_CI_AS
> >
> > q1: select dt_column,vc_colomn from mytable where vc_column is null
> > ->result; >20.000 records where vc_column indeed is null
> >
> > but, if i expand the query with a date clause like so:
> > q2: select dt_column,vc_column from mytable where vc_column is null and
> > year(dt_column) = '2006'
> > ->result; <20.000 records where SOME of the results DO have a value for
> > the vc_column!
> >
> > This is strange isnt it ?
> >
> > I already have a solution to overcome this; but I do not see why i have
> > to do this:
> > When I cast the vc_column to a varchar like so:
> > q3: select dt_column,vc_column from mytable where cast(vc_column as
> > varchar) and year(dt_column) ='2006'
> > ->the result is good! only null values for the vc_column !
> > but why do i have to cast a varchar column to a varchar before the is
> > null will work '?
> >
> > Thanks very much,
> > Jeroen
> >|||Hi
You are currently on service pack 3a, you can apply service pack 4
http://www.microsoft.com/downloads/details.aspx?familyid=8E2DFC8D-C20E-4446-99A9-B7F0213F8BC5&displaylang=en
followed by the subsequent hot fixes. I would recommend at least going to
build 2040. This is the link for the 2187 download:
http://www.microsoft.com/downloads/details.aspx?familyid=9C9AB140-BDEE-44DF-B7A3-E6849297754A&displaylang=en
John
"Shuwi" wrote:
> Hi Keith,
> Thanks for the quick reply;
> The version of sql server is:
> Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002
> 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Enterprise
> Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> on the > http://www.aspfaq.com/sql2000Builds.asp website I can see no
> hotfixes available for this release...?
> (seems to stop at build 2187)...
> Maybe the 2187 hotfix works here to; I'll test; thanks again.
> Jeroen
> Keith Kratochvil wrote:
> > This sounds a bit familiar. I ran into a similar problem where unexpected
> > results were returned from a query (that was a bit more complex than the one
> > you posted).
> >
> > What version of SQL Server 2000 are you running?
> > execute this within Query Analyzer:
> > SELECT @.@.version
> > and compare the results to the build list here:
> > http://www.aspfaq.com/sql2000Builds.asp
> >
> > In our case we experienced the error on SP4 (SP3 worked fine). Applying the
> > .2187 hotfix solved our problem. Do you have a test system that you can use
> > to reproduce the probem and test various patches to see if they solve your
> > problem?
> >
> >
> > --
> > Keith Kratochvil
> >
> >
> > "Shuwi" <jeroen.schoenmakers@.gmail.com> wrote in message
> > news:1160054422.157730.217980@.c28g2000cwb.googlegroups.com...
> > > Hello,
> > >
> > > My problem is; weird results with a IS NULL clause in a query.
> > >
> > > I have a sql2000 dbase, table, 2 columns and the following query:
> > > dt_column => > > type: datetime
> > > computed: no
> > > length:8
> > > nullable: no
> > > TrimTrailingBlanks:n/a
> > > FixedLenNullnSource:n/a
> > > Collation: null
> > >
> > > vc_column => > > type:varchar
> > > computed: no
> > > length:15
> > > nullable: yes
> > > TrimTrailingBlanks:no
> > > FixedLenNullnSource: no
> > > Collation: SQL_Latin1_General_CP1_CI_AS
> > >
> > > q1: select dt_column,vc_colomn from mytable where vc_column is null
> > > ->result; >20.000 records where vc_column indeed is null
> > >
> > > but, if i expand the query with a date clause like so:
> > > q2: select dt_column,vc_column from mytable where vc_column is null and
> > > year(dt_column) = '2006'
> > > ->result; <20.000 records where SOME of the results DO have a value for
> > > the vc_column!
> > >
> > > This is strange isnt it ?
> > >
> > > I already have a solution to overcome this; but I do not see why i have
> > > to do this:
> > > When I cast the vc_column to a varchar like so:
> > > q3: select dt_column,vc_column from mytable where cast(vc_column as
> > > varchar) and year(dt_column) ='2006'
> > > ->the result is good! only null values for the vc_column !
> > > but why do i have to cast a varchar column to a varchar before the is
> > > null will work '?
> > >
> > > Thanks very much,
> > > Jeroen
> > >
>|||Don't be confused by "Service Pack 4" in the results. That is the WINDOWS
service pack, not the SQL Server Service pack.
Here is another select statement that returns database service pack level:
select serverproperty('productlevel')
By the way,
.760 is SP3a
There are a few publically available hotfixes for SP3:
.818
.878
You could upgrade to SP4 (version 2039)
There are two publically available hotfixes for SP4: 2040 and 2187
--
Keith Kratochvil
"Shuwi" <jeroen.schoenmakers@.gmail.com> wrote in message
news:1160056347.136146.322120@.h48g2000cwc.googlegroups.com...
> Hi Keith,
> Thanks for the quick reply;
> The version of sql server is:
> Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002
> 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Enterprise
> Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> on the > http://www.aspfaq.com/sql2000Builds.asp website I can see no
> hotfixes available for this release...?
> (seems to stop at build 2187)...
> Maybe the 2187 hotfix works here to; I'll test; thanks again.
> Jeroen
> Keith Kratochvil wrote:
>> This sounds a bit familiar. I ran into a similar problem where
>> unexpected
>> results were returned from a query (that was a bit more complex than the
>> one
>> you posted).
>> What version of SQL Server 2000 are you running?
>> execute this within Query Analyzer:
>> SELECT @.@.version
>> and compare the results to the build list here:
>> http://www.aspfaq.com/sql2000Builds.asp
>> In our case we experienced the error on SP4 (SP3 worked fine). Applying
>> the
>> .2187 hotfix solved our problem. Do you have a test system that you can
>> use
>> to reproduce the probem and test various patches to see if they solve
>> your
>> problem?
>>
>> --
>> Keith Kratochvil
>>
>> "Shuwi" <jeroen.schoenmakers@.gmail.com> wrote in message
>> news:1160054422.157730.217980@.c28g2000cwb.googlegroups.com...
>> > Hello,
>> >
>> > My problem is; weird results with a IS NULL clause in a query.
>> >
>> > I have a sql2000 dbase, table, 2 columns and the following query:
>> > dt_column =>> > type: datetime
>> > computed: no
>> > length:8
>> > nullable: no
>> > TrimTrailingBlanks:n/a
>> > FixedLenNullnSource:n/a
>> > Collation: null
>> >
>> > vc_column =>> > type:varchar
>> > computed: no
>> > length:15
>> > nullable: yes
>> > TrimTrailingBlanks:no
>> > FixedLenNullnSource: no
>> > Collation: SQL_Latin1_General_CP1_CI_AS
>> >
>> > q1: select dt_column,vc_colomn from mytable where vc_column is null
>> > ->result; >20.000 records where vc_column indeed is null
>> >
>> > but, if i expand the query with a date clause like so:
>> > q2: select dt_column,vc_column from mytable where vc_column is null and
>> > year(dt_column) = '2006'
>> > ->result; <20.000 records where SOME of the results DO have a value for
>> > the vc_column!
>> >
>> > This is strange isnt it ?
>> >
>> > I already have a solution to overcome this; but I do not see why i have
>> > to do this:
>> > When I cast the vc_column to a varchar like so:
>> > q3: select dt_column,vc_column from mytable where cast(vc_column as
>> > varchar) and year(dt_column) ='2006'
>> > ->the result is good! only null values for the vc_column !
>> > but why do i have to cast a varchar column to a varchar before the is
>> > null will work '?
>> >
>> > Thanks very much,
>> > Jeroen
>> >
>|||Thanks all;
Seems I have some upgrading to do...
Kind regards,
Jeroen
Keith Kratochvil wrote:
> Don't be confused by "Service Pack 4" in the results. That is the WINDOWS
> service pack, not the SQL Server Service pack.
> Here is another select statement that returns database service pack level:
> select serverproperty('productlevel')
> By the way,
> .760 is SP3a
> There are a few publically available hotfixes for SP3:
> .818
> .878
> You could upgrade to SP4 (version 2039)
> There are two publically available hotfixes for SP4: 2040 and 2187
> --
> Keith Kratochvil
>
> "Shuwi" <jeroen.schoenmakers@.gmail.com> wrote in message
> news:1160056347.136146.322120@.h48g2000cwc.googlegroups.com...
> > Hi Keith,
> >
> > Thanks for the quick reply;
> > The version of sql server is:
> >
> > Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002
> > 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Enterprise
> > Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> >
> > on the > http://www.aspfaq.com/sql2000Builds.asp website I can see no
> > hotfixes available for this release...?
> > (seems to stop at build 2187)...
> >
> > Maybe the 2187 hotfix works here to; I'll test; thanks again.
> >
> > Jeroen
> > Keith Kratochvil wrote:
> >> This sounds a bit familiar. I ran into a similar problem where
> >> unexpected
> >> results were returned from a query (that was a bit more complex than the
> >> one
> >> you posted).
> >>
> >> What version of SQL Server 2000 are you running?
> >> execute this within Query Analyzer:
> >> SELECT @.@.version
> >> and compare the results to the build list here:
> >> http://www.aspfaq.com/sql2000Builds.asp
> >>
> >> In our case we experienced the error on SP4 (SP3 worked fine). Applying
> >> the
> >> .2187 hotfix solved our problem. Do you have a test system that you can
> >> use
> >> to reproduce the probem and test various patches to see if they solve
> >> your
> >> problem?
> >>
> >>
> >> --
> >> Keith Kratochvil
> >>
> >>
> >> "Shuwi" <jeroen.schoenmakers@.gmail.com> wrote in message
> >> news:1160054422.157730.217980@.c28g2000cwb.googlegroups.com...
> >> > Hello,
> >> >
> >> > My problem is; weird results with a IS NULL clause in a query.
> >> >
> >> > I have a sql2000 dbase, table, 2 columns and the following query:
> >> > dt_column => >> > type: datetime
> >> > computed: no
> >> > length:8
> >> > nullable: no
> >> > TrimTrailingBlanks:n/a
> >> > FixedLenNullnSource:n/a
> >> > Collation: null
> >> >
> >> > vc_column => >> > type:varchar
> >> > computed: no
> >> > length:15
> >> > nullable: yes
> >> > TrimTrailingBlanks:no
> >> > FixedLenNullnSource: no
> >> > Collation: SQL_Latin1_General_CP1_CI_AS
> >> >
> >> > q1: select dt_column,vc_colomn from mytable where vc_column is null
> >> > ->result; >20.000 records where vc_column indeed is null
> >> >
> >> > but, if i expand the query with a date clause like so:
> >> > q2: select dt_column,vc_column from mytable where vc_column is null and
> >> > year(dt_column) = '2006'
> >> > ->result; <20.000 records where SOME of the results DO have a value for
> >> > the vc_column!
> >> >
> >> > This is strange isnt it ?
> >> >
> >> > I already have a solution to overcome this; but I do not see why i have
> >> > to do this:
> >> > When I cast the vc_column to a varchar like so:
> >> > q3: select dt_column,vc_column from mytable where cast(vc_column as
> >> > varchar) and year(dt_column) ='2006'
> >> > ->the result is good! only null values for the vc_column !
> >> > but why do i have to cast a varchar column to a varchar before the is
> >> > null will work '?
> >> >
> >> > Thanks very much,
> >> > Jeroen
> >> >
> >

IS NULL bug(?)

Hello,
My problem is; weird results with a IS NULL clause in a query.
I have a sql2000 dbase, table, 2 columns and the following query:
dt_column =
type: datetime
computed: no
length:8
nullable: no
TrimTrailingBlanks:n/a
FixedLenNullnSource:n/a
Collation: null
vc_column =
type:varchar
computed: no
length:15
nullable: yes
TrimTrailingBlanks:no
FixedLenNullnSource:no
Collation: SQL_Latin1_General_CP1_CI_AS
q1: select dt_column,vc_colomn from mytable where vc_column is null
->result; >20.000 records where vc_column indeed is null
but, if i expand the query with a date clause like so:
q2: select dt_column,vc_column from mytable where vc_column is null and
year(dt_column) = '2006'
->result; <20.000 records where SOME of the results DO have a value for
the vc_column!
This is strange isnt it ?
I already have a solution to overcome this; but I do not see why i have
to do this:
When I cast the vc_column to a varchar like so:
q3: select dt_column,vc_column from mytable where cast(vc_column as
varchar) and year(dt_column) ='2006'
->the result is good! only null values for the vc_column !
but why do i have to cast a varchar column to a varchar before the is
null will work ??
Thanks very much,
Jeroen
This sounds a bit familiar. I ran into a similar problem where unexpected
results were returned from a query (that was a bit more complex than the one
you posted).
What version of SQL Server 2000 are you running?
execute this within Query Analyzer:
SELECT @.@.version
and compare the results to the build list here:
http://www.aspfaq.com/sql2000Builds.asp
In our case we experienced the error on SP4 (SP3 worked fine). Applying the
..2187 hotfix solved our problem. Do you have a test system that you can use
to reproduce the probem and test various patches to see if they solve your
problem?
Keith Kratochvil
"Shuwi" <jeroen.schoenmakers@.gmail.com> wrote in message
news:1160054422.157730.217980@.c28g2000cwb.googlegr oups.com...
> Hello,
> My problem is; weird results with a IS NULL clause in a query.
> I have a sql2000 dbase, table, 2 columns and the following query:
> dt_column =
> type: datetime
> computed: no
> length:8
> nullable: no
> TrimTrailingBlanks:n/a
> FixedLenNullnSource:n/a
> Collation: null
> vc_column =
> type:varchar
> computed: no
> length:15
> nullable: yes
> TrimTrailingBlanks:no
> FixedLenNullnSource: no
> Collation: SQL_Latin1_General_CP1_CI_AS
> q1: select dt_column,vc_colomn from mytable where vc_column is null
> ->result; >20.000 records where vc_column indeed is null
> but, if i expand the query with a date clause like so:
> q2: select dt_column,vc_column from mytable where vc_column is null and
> year(dt_column) = '2006'
> ->result; <20.000 records where SOME of the results DO have a value for
> the vc_column!
> This is strange isnt it ?
> I already have a solution to overcome this; but I do not see why i have
> to do this:
> When I cast the vc_column to a varchar like so:
> q3: select dt_column,vc_column from mytable where cast(vc_column as
> varchar) and year(dt_column) ='2006'
> ->the result is good! only null values for the vc_column !
> but why do i have to cast a varchar column to a varchar before the is
> null will work ??
> Thanks very much,
> Jeroen
>
|||Hi Keith,
Thanks for the quick reply;
The version of sql server is:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002
14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Enterprise
Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
on the > http://www.aspfaq.com/sql2000Builds.asp website I can see no
hotfixes available for this release...?
(seems to stop at build 2187)...
Maybe the 2187 hotfix works here to; I'll test; thanks again.
Jeroen
Keith Kratochvil wrote:[vbcol=seagreen]
> This sounds a bit familiar. I ran into a similar problem where unexpected
> results were returned from a query (that was a bit more complex than the one
> you posted).
> What version of SQL Server 2000 are you running?
> execute this within Query Analyzer:
> SELECT @.@.version
> and compare the results to the build list here:
> http://www.aspfaq.com/sql2000Builds.asp
> In our case we experienced the error on SP4 (SP3 worked fine). Applying the
> .2187 hotfix solved our problem. Do you have a test system that you can use
> to reproduce the probem and test various patches to see if they solve your
> problem?
>
> --
> Keith Kratochvil
>
> "Shuwi" <jeroen.schoenmakers@.gmail.com> wrote in message
> news:1160054422.157730.217980@.c28g2000cwb.googlegr oups.com...
|||Hi
You are currently on service pack 3a, you can apply service pack 4
http://www.microsoft.com/downloads/d...displaylang=en
followed by the subsequent hot fixes. I would recommend at least going to
build 2040. This is the link for the 2187 download:
http://www.microsoft.com/downloads/d...displaylang=en
John
"Shuwi" wrote:

> Hi Keith,
> Thanks for the quick reply;
> The version of sql server is:
> Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002
> 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Enterprise
> Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> on the > http://www.aspfaq.com/sql2000Builds.asp website I can see no
> hotfixes available for this release...?
> (seems to stop at build 2187)...
> Maybe the 2187 hotfix works here to; I'll test; thanks again.
> Jeroen
> Keith Kratochvil wrote:
>
|||Don't be confused by "Service Pack 4" in the results. That is the WINDOWS
service pack, not the SQL Server Service pack.
Here is another select statement that returns database service pack level:
select serverproperty('productlevel')
By the way,
..760 is SP3a
There are a few publically available hotfixes for SP3:
.818
.878
You could upgrade to SP4 (version 2039)
There are two publically available hotfixes for SP4: 2040 and 2187
Keith Kratochvil
"Shuwi" <jeroen.schoenmakers@.gmail.com> wrote in message
news:1160056347.136146.322120@.h48g2000cwc.googlegr oups.com...
> Hi Keith,
> Thanks for the quick reply;
> The version of sql server is:
> Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002
> 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Enterprise
> Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> on the > http://www.aspfaq.com/sql2000Builds.asp website I can see no
> hotfixes available for this release...?
> (seems to stop at build 2187)...
> Maybe the 2187 hotfix works here to; I'll test; thanks again.
> Jeroen
> Keith Kratochvil wrote:
>
|||Thanks all;
Seems I have some upgrading to do...
Kind regards,
Jeroen
Keith Kratochvil wrote:[vbcol=seagreen]
> Don't be confused by "Service Pack 4" in the results. That is the WINDOWS
> service pack, not the SQL Server Service pack.
> Here is another select statement that returns database service pack level:
> select serverproperty('productlevel')
> By the way,
> .760 is SP3a
> There are a few publically available hotfixes for SP3:
> .818
> .878
> You could upgrade to SP4 (version 2039)
> There are two publically available hotfixes for SP4: 2040 and 2187
> --
> Keith Kratochvil
>
> "Shuwi" <jeroen.schoenmakers@.gmail.com> wrote in message
> news:1160056347.136146.322120@.h48g2000cwc.googlegr oups.com...

IS NULL bug(?)

Hello,
My problem is; weird results with a IS NULL clause in a query.
I have a sql2000 dbase, table, 2 columns and the following query:
dt_column =
type: datetime
computed: no
length:8
nullable: no
TrimTrailingBlanks:n/a
FixedLenNullnSource:n/a
Collation: null
vc_column =
type:varchar
computed: no
length:15
nullable: yes
TrimTrailingBlanks:no
FixedLenNullnSource: no
Collation: SQL_Latin1_General_CP1_CI_AS
q1: select dt_column,vc_colomn from mytable where vc_column is null
->result; >20.000 records where vc_column indeed is null
but, if i expand the query with a date clause like so:
q2: select dt_column,vc_column from mytable where vc_column is null and
year(dt_column) = '2006'
->result; <20.000 records where SOME of the results DO have a value for
the vc_column!
This is strange isnt it ?
I already have a solution to overcome this; but I do not see why i have
to do this:
When I cast the vc_column to a varchar like so:
q3: select dt_column,vc_column from mytable where cast(vc_column as
varchar) and year(dt_column) ='2006'
->the result is good! only null values for the vc_column !
but why do i have to cast a varchar column to a varchar before the is
null will work '?
Thanks very much,
JeroenThis sounds a bit familiar. I ran into a similar problem where unexpected
results were returned from a query (that was a bit more complex than the one
you posted).
What version of SQL Server 2000 are you running?
execute this within Query Analyzer:
SELECT @.@.version
and compare the results to the build list here:
http://www.aspfaq.com/sql2000Builds.asp
In our case we experienced the error on SP4 (SP3 worked fine). Applying the
.2187 hotfix solved our problem. Do you have a test system that you can us
e
to reproduce the probem and test various patches to see if they solve your
problem?
Keith Kratochvil
"Shuwi" <jeroen.schoenmakers@.gmail.com> wrote in message
news:1160054422.157730.217980@.c28g2000cwb.googlegroups.com...
> Hello,
> My problem is; weird results with a IS NULL clause in a query.
> I have a sql2000 dbase, table, 2 columns and the following query:
> dt_column =
> type: datetime
> computed: no
> length:8
> nullable: no
> TrimTrailingBlanks:n/a
> FixedLenNullnSource:n/a
> Collation: null
> vc_column =
> type:varchar
> computed: no
> length:15
> nullable: yes
> TrimTrailingBlanks:no
> FixedLenNullnSource: no
> Collation: SQL_Latin1_General_CP1_CI_AS
> q1: select dt_column,vc_colomn from mytable where vc_column is null
> ->result; >20.000 records where vc_column indeed is null
> but, if i expand the query with a date clause like so:
> q2: select dt_column,vc_column from mytable where vc_column is null and
> year(dt_column) = '2006'
> ->result; <20.000 records where SOME of the results DO have a value for
> the vc_column!
> This is strange isnt it ?
> I already have a solution to overcome this; but I do not see why i have
> to do this:
> When I cast the vc_column to a varchar like so:
> q3: select dt_column,vc_column from mytable where cast(vc_column as
> varchar) and year(dt_column) ='2006'
> ->the result is good! only null values for the vc_column !
> but why do i have to cast a varchar column to a varchar before the is
> null will work '?
> Thanks very much,
> Jeroen
>|||Hi Keith,
Thanks for the quick reply;
The version of sql server is:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002
14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Enterprise
Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
on the > http://www.aspfaq.com/sql2000Builds.asp website I can see no
hotfixes available for this release...?
(seems to stop at build 2187)...
Maybe the 2187 hotfix works here to; I'll test; thanks again.
Jeroen
Keith Kratochvil wrote:[vbcol=seagreen]
> This sounds a bit familiar. I ran into a similar problem where unexpected
> results were returned from a query (that was a bit more complex than the o
ne
> you posted).
> What version of SQL Server 2000 are you running?
> execute this within Query Analyzer:
> SELECT @.@.version
> and compare the results to the build list here:
> http://www.aspfaq.com/sql2000Builds.asp
> In our case we experienced the error on SP4 (SP3 worked fine). Applying t
he
> .2187 hotfix solved our problem. Do you have a test system that you can u
se
> to reproduce the probem and test various patches to see if they solve your
> problem?
>
> --
> Keith Kratochvil
>
> "Shuwi" <jeroen.schoenmakers@.gmail.com> wrote in message
> news:1160054422.157730.217980@.c28g2000cwb.googlegroups.com...|||Hi
You are currently on service pack 3a, you can apply service pack 4
http://www.microsoft.com/downloads/...&displaylang=en
followed by the subsequent hot fixes. I would recommend at least going to
build 2040. This is the link for the 2187 download:
http://www.microsoft.com/downloads/...&displaylang=en
John
"Shuwi" wrote:

> Hi Keith,
> Thanks for the quick reply;
> The version of sql server is:
> Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002
> 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Enterprise
> Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> on the > http://www.aspfaq.com/sql2000Builds.asp website I can see no
> hotfixes available for this release...?
> (seems to stop at build 2187)...
> Maybe the 2187 hotfix works here to; I'll test; thanks again.
> Jeroen
> Keith Kratochvil wrote:
>|||Don't be confused by "Service Pack 4" in the results. That is the WINDOWS
service pack, not the SQL Server Service pack.
Here is another select statement that returns database service pack level:
select serverproperty('productlevel')
By the way,
.760 is SP3a
There are a few publically available hotfixes for SP3:
.818
.878
You could upgrade to SP4 (version 2039)
There are two publically available hotfixes for SP4: 2040 and 2187
Keith Kratochvil
"Shuwi" <jeroen.schoenmakers@.gmail.com> wrote in message
news:1160056347.136146.322120@.h48g2000cwc.googlegroups.com...
> Hi Keith,
> Thanks for the quick reply;
> The version of sql server is:
> Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002
> 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Enterprise
> Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> on the > http://www.aspfaq.com/sql2000Builds.asp website I can see no
> hotfixes available for this release...?
> (seems to stop at build 2187)...
> Maybe the 2187 hotfix works here to; I'll test; thanks again.
> Jeroen
> Keith Kratochvil wrote:
>|||Thanks all;
Seems I have some upgrading to do...
Kind regards,
Jeroen
Keith Kratochvil wrote:[vbcol=seagreen]
> Don't be confused by "Service Pack 4" in the results. That is the WINDOWS
> service pack, not the SQL Server Service pack.
> Here is another select statement that returns database service pack level:
> select serverproperty('productlevel')
> By the way,
> .760 is SP3a
> There are a few publically available hotfixes for SP3:
> .818
> .878
> You could upgrade to SP4 (version 2039)
> There are two publically available hotfixes for SP4: 2040 and 2187
> --
> Keith Kratochvil
>
> "Shuwi" <jeroen.schoenmakers@.gmail.com> wrote in message
> news:1160056347.136146.322120@.h48g2000cwc.googlegroups.com...