Re: major bug in SQL 2000

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Tibor Karaszi (tibor_please.no.email_karaszi_at_hotmail.nomail.com)
Date: 05/13/04 

Date: Thu, 13 May 2004 12:51:04 +0200

If you post a complete repro script, we can try it on our SQL Servers and see if it reproduces... 

-- 
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Franc v/d Westelaken" <fvdwestelaken@hotmail.com> wrote in message
news:40a35050.87859203@msnews.microsoft.com...
> Hi,
>
> this is the SQL statement I'm using:
>
> SELECT     TOP 100 PERCENT dbo.tblWoningen.*, dbo.Huren.*,
> dbo.tblPuntenTotaal.*,
>                       dbo.Woningen.Perceel AS Expr1
> FROM         dbo.Woningen LEFT OUTER JOIN
>                       dbo.Huren ON
>                       dbo.Woningen.Perceel = dbo.Huren.Perceelnr# LEFT
> OUTER JOIN
>                       dbo.tblPuntenTotaal ON dbo.Woningen.Perceel =
> dbo.tblPuntenTotaal.VHE_nummer
> ORDER BY dbo.Woningen.Perceel
>
> Franc.
>
> >Can we see your code please.
> >
> >J
> >
> >
> >>-----Original Message-----
> >>I have screenshots available fot those interested. So far
> >I've found 4
> >>views which were affected. They were all based on the
> >same tables. I
> >>ran a dbcc checkdb and no error are reported on the
> >database.
> >>
> >>Franc.
> >>
> >>>Hi,
> >>>
> >>>today I discovered a major and dangerous bug in SQL
> >server. I've
> >>>created a view with many fields. When looking in the
> >design manager
> >>>everything looks fine. However when I use the view, one
> >of the column
> >>>headings is missing and the column names are shift to
> >the left. The
> >>>values however are still on their own place. This
> >results in a major
> >>>issue that the values appear under the wrong column. In
> >design view
> >>>everything looks fine, but when you open the query it
> >display the
> >>>wrong values. Thus:
> >>>
> >>>In design view it looks like this:
> >>>
> >>>Field1 Field2 Field3 Field4
> >>>1 2 3 4
> >>>
> >>>When opening the query it looks like this:
> >>>
> >>>Field1 Field3 Field4
> >>>1 2 3
> >>>
> >>>How the hell is this possible. Changing one thing in the
> >view saving
> >>>it again and then opneing it, everything is fine. But
> >how do I know
> >>>which views are affected ?
> >>>
> >>>Franc.
> >>
> >>.
> >>
>

Relevant Pages

  • Re: Access Denied etc. - appears to be Server 2003 SP1 problem
    ... We are also having this problem with our 2003 SP1 SQL servers. ... > Service and Query Lock permissions on the SCM he gets a "Service Control: ...
    (microsoft.public.sqlserver.clustering)
  • Re: Error 3146 (VB6)
    ... Using DAO 3.6, the problem occurs. ... part of the problem - but of course that also runs the risk of query never ... VB and somehow automating MSAccess, ... Normally when we have to use multiple SQL Servers for a query - we do it ...
    (microsoft.public.vb.database.dao)
  • moving data between servers
    ... I have a query on the best way for moving data across the SQL Servers. ... the data in a dataset and use it's WriteXML method to generate an XML file. ...
    (microsoft.public.dotnet.framework.adonet)
  • RE: Query execution plan different between production/test - same data
    ... The same query can behave differently on different boxes ... have the same kind of data and data distribution? ... * How often are statistics updated on the good and bad sql servers? ...
    (microsoft.public.sqlserver.server)