bar chart problem, different bar length at same imput value

I have a bar chart, displaying different bar length with same value ( 5
input with exact same value but in different series group ). Please help.
--
SincerelyFrank,
Are you sure you are not mixing data, category, and series fields?
Regards,
Cem
"Frank RS" <FrankRS@.discussions.microsoft.com> wrote in message
news:E708D16C-3261-4993-B1E9-A8A1EE4A7465@.microsoft.com...
> I have a bar chart, displaying different bar length with same value ( 5
> input with exact same value but in different series group ). Please help.
> --
> Sincerely|||It is a tabular table with two columns, ProductID and
SalesAmountPercentageChange.
I put the SalesAmountPercentageChange in the "values", and ProductID into
the "Series" field. (If I put the ProductID into the "group", the bars are
displayed in same color, which I want it different)
Thanks in advance for any further help.
"Cem Demircioglu" wrote:
> Frank,
> Are you sure you are not mixing data, category, and series fields?
> Regards,
> Cem
> "Frank RS" <FrankRS@.discussions.microsoft.com> wrote in message
> news:E708D16C-3261-4993-B1E9-A8A1EE4A7465@.microsoft.com...
> >
> > I have a bar chart, displaying different bar length with same value ( 5
> > input with exact same value but in different series group ). Please help.
> >
> > --
> > Sincerely
>
>

Bad Page error

I am getting an error in my DTS logs about a bad page. Here is the exact
message.
Step Error Description:I/O error (bad page ID) detected during read at
offset 0x0000022a040000 in file 'E:\SQLData\ALS_Stage_Data.MDF'.
We are getting this error on 2 different servers. The process has been
running like a champ for years and now we are getting this message. All that
is running when it errors out is an update statement that is joining 2
tables. I have read some about tempdb running into these issues and it
suggests that there may be hardware issues. That is not the case as we have
looked into that and we have many other processes that run on these servers.
I have also read that service pack 4 needs to be installed. Well we moved
our process to another server with exactly the same configuration and it ran
fine on there. Had anybody else ran into this? Any suggestions? All help
is appreciated.
Thankshave you run DBCC CHECKDB to see if there are any errors?
--
Jack Vamvas
__________________________________________________________________
Receive free SQL tips - register at www.ciquery.com/sqlserver.htm
SQL Server Performance Audit - check www.ciquery.com/sqlserver_audit.htm
New article by Jack Vamvas - SQL and Markov Chains -
www.ciquery.com/articles/art_04.asp
"Andy" <Andy@.discussions.microsoft.com> wrote in message
news:AA513080-F72F-4386-93CA-93CEF0673F76@.microsoft.com...
> I am getting an error in my DTS logs about a bad page. Here is the exact
> message.
> Step Error Description:I/O error (bad page ID) detected during read at
> offset 0x0000022a040000 in file 'E:\SQLData\ALS_Stage_Data.MDF'.
> We are getting this error on 2 different servers. The process has been
> running like a champ for years and now we are getting this message. All
that
> is running when it errors out is an update statement that is joining 2
> tables. I have read some about tempdb running into these issues and it
> suggests that there may be hardware issues. That is not the case as we
have
> looked into that and we have many other processes that run on these
servers.
> I have also read that service pack 4 needs to be installed. Well we moved
> our process to another server with exactly the same configuration and it
ran
> fine on there. Had anybody else ran into this? Any suggestions? All
help
> is appreciated.
> Thanks|||Yes, we ran that and no errors were returned. We also ran it with Allow data
loss and no errors were returned. Like I mentioned below, this is happening
on 2 servers. It is the same process, but 1 is the dev server and 1 is prod.
"Jack Vamvas" wrote:
> have you run DBCC CHECKDB to see if there are any errors?
> --
> Jack Vamvas
> __________________________________________________________________
> Receive free SQL tips - register at www.ciquery.com/sqlserver.htm
> SQL Server Performance Audit - check www.ciquery.com/sqlserver_audit.htm
> New article by Jack Vamvas - SQL and Markov Chains -
> www.ciquery.com/articles/art_04.asp
> "Andy" <Andy@.discussions.microsoft.com> wrote in message
> news:AA513080-F72F-4386-93CA-93CEF0673F76@.microsoft.com...
> > I am getting an error in my DTS logs about a bad page. Here is the exact
> > message.
> >
> > Step Error Description:I/O error (bad page ID) detected during read at
> > offset 0x0000022a040000 in file 'E:\SQLData\ALS_Stage_Data.MDF'.
> >
> > We are getting this error on 2 different servers. The process has been
> > running like a champ for years and now we are getting this message. All
> that
> > is running when it errors out is an update statement that is joining 2
> > tables. I have read some about tempdb running into these issues and it
> > suggests that there may be hardware issues. That is not the case as we
> have
> > looked into that and we have many other processes that run on these
> servers.
> > I have also read that service pack 4 needs to be installed. Well we moved
> > our process to another server with exactly the same configuration and it
> ran
> > fine on there. Had anybody else ran into this? Any suggestions? All
> help
> > is appreciated.
> >
> > Thanks
>
>|||Hi Andy,
This is usually caused by the hardware, but if it is happening on two
different hardware systems, it seems like a logical problem in the database.
You probably restored a backup of the database from server to another.
Here is the logical meaning of this error:
http://support.microsoft.com/default.aspx?scid=kb;en-us;828339
HTH
DeeJay Puar
MCDBA
(bad page ID): This message means that the pageID on the page header is not
the expected page that was read from the disk. For example, if SQL Server
2000 provides a file offset for database file 1 that is for logical page 100,
the pageID on the page header for that 8 KB page should be 1:100. If not, the
bad page ID is included in the logical I/O check failure message.
You can read more about it here:
"Andy" wrote:
> Yes, we ran that and no errors were returned. We also ran it with Allow data
> loss and no errors were returned. Like I mentioned below, this is happening
> on 2 servers. It is the same process, but 1 is the dev server and 1 is prod.
>
> "Jack Vamvas" wrote:
> > have you run DBCC CHECKDB to see if there are any errors?
> >
> > --
> > Jack Vamvas
> > __________________________________________________________________
> > Receive free SQL tips - register at www.ciquery.com/sqlserver.htm
> > SQL Server Performance Audit - check www.ciquery.com/sqlserver_audit.htm
> > New article by Jack Vamvas - SQL and Markov Chains -
> > www.ciquery.com/articles/art_04.asp
> > "Andy" <Andy@.discussions.microsoft.com> wrote in message
> > news:AA513080-F72F-4386-93CA-93CEF0673F76@.microsoft.com...
> > > I am getting an error in my DTS logs about a bad page. Here is the exact
> > > message.
> > >
> > > Step Error Description:I/O error (bad page ID) detected during read at
> > > offset 0x0000022a040000 in file 'E:\SQLData\ALS_Stage_Data.MDF'.
> > >
> > > We are getting this error on 2 different servers. The process has been
> > > running like a champ for years and now we are getting this message. All
> > that
> > > is running when it errors out is an update statement that is joining 2
> > > tables. I have read some about tempdb running into these issues and it
> > > suggests that there may be hardware issues. That is not the case as we
> > have
> > > looked into that and we have many other processes that run on these
> > servers.
> > > I have also read that service pack 4 needs to be installed. Well we moved
> > > our process to another server with exactly the same configuration and it
> > ran
> > > fine on there. Had anybody else ran into this? Any suggestions? All
> > help
> > > is appreciated.
> > >
> > > Thanks
> >
> >
> >|||I looked into that as well, as I thought I did take a backup. The 2nd server
that it is happening on I created brand new databases before I kicked off the
process and we received the same error, at the same point in the process.
"DeeJay Puar" wrote:
> Hi Andy,
> This is usually caused by the hardware, but if it is happening on two
> different hardware systems, it seems like a logical problem in the database.
> You probably restored a backup of the database from server to another.
> Here is the logical meaning of this error:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;828339
> HTH
> DeeJay Puar
> MCDBA
> (bad page ID): This message means that the pageID on the page header is not
> the expected page that was read from the disk. For example, if SQL Server
> 2000 provides a file offset for database file 1 that is for logical page 100,
> the pageID on the page header for that 8 KB page should be 1:100. If not, the
> bad page ID is included in the logical I/O check failure message.
> You can read more about it here:
>
> "Andy" wrote:
> > Yes, we ran that and no errors were returned. We also ran it with Allow data
> > loss and no errors were returned. Like I mentioned below, this is happening
> > on 2 servers. It is the same process, but 1 is the dev server and 1 is prod.
> >
> >
> > "Jack Vamvas" wrote:
> >
> > > have you run DBCC CHECKDB to see if there are any errors?
> > >
> > > --
> > > Jack Vamvas
> > > __________________________________________________________________
> > > Receive free SQL tips - register at www.ciquery.com/sqlserver.htm
> > > SQL Server Performance Audit - check www.ciquery.com/sqlserver_audit.htm
> > > New article by Jack Vamvas - SQL and Markov Chains -
> > > www.ciquery.com/articles/art_04.asp
> > > "Andy" <Andy@.discussions.microsoft.com> wrote in message
> > > news:AA513080-F72F-4386-93CA-93CEF0673F76@.microsoft.com...
> > > > I am getting an error in my DTS logs about a bad page. Here is the exact
> > > > message.
> > > >
> > > > Step Error Description:I/O error (bad page ID) detected during read at
> > > > offset 0x0000022a040000 in file 'E:\SQLData\ALS_Stage_Data.MDF'.
> > > >
> > > > We are getting this error on 2 different servers. The process has been
> > > > running like a champ for years and now we are getting this message. All
> > > that
> > > > is running when it errors out is an update statement that is joining 2
> > > > tables. I have read some about tempdb running into these issues and it
> > > > suggests that there may be hardware issues. That is not the case as we
> > > have
> > > > looked into that and we have many other processes that run on these
> > > servers.
> > > > I have also read that service pack 4 needs to be installed. Well we moved
> > > > our process to another server with exactly the same configuration and it
> > > ran
> > > > fine on there. Had anybody else ran into this? Any suggestions? All
> > > help
> > > > is appreciated.
> > > >
> > > > Thanks
> > >
> > >
> > >|||No too sure as to what is happening. I can not really duplicate it here.
On the server, did you take a backup from the old server and restore the
database on the new server? Or did you just create a shell and then ran your
dts package to load the data? Have you looked at the source tables in the DTS
package?
Have you looked into torn-page?
"Andy" wrote:
> I looked into that as well, as I thought I did take a backup. The 2nd server
> that it is happening on I created brand new databases before I kicked off the
> process and we received the same error, at the same point in the process.
> "DeeJay Puar" wrote:
> > Hi Andy,
> >
> > This is usually caused by the hardware, but if it is happening on two
> > different hardware systems, it seems like a logical problem in the database.
> > You probably restored a backup of the database from server to another.
> >
> > Here is the logical meaning of this error:
> >
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;828339
> >
> > HTH
> >
> > DeeJay Puar
> > MCDBA
> >
> > (bad page ID): This message means that the pageID on the page header is not
> > the expected page that was read from the disk. For example, if SQL Server
> > 2000 provides a file offset for database file 1 that is for logical page 100,
> > the pageID on the page header for that 8 KB page should be 1:100. If not, the
> > bad page ID is included in the logical I/O check failure message.
> >
> > You can read more about it here:
> >
> >
> >
> > "Andy" wrote:
> >
> > > Yes, we ran that and no errors were returned. We also ran it with Allow data
> > > loss and no errors were returned. Like I mentioned below, this is happening
> > > on 2 servers. It is the same process, but 1 is the dev server and 1 is prod.
> > >
> > >
> > > "Jack Vamvas" wrote:
> > >
> > > > have you run DBCC CHECKDB to see if there are any errors?
> > > >
> > > > --
> > > > Jack Vamvas
> > > > __________________________________________________________________
> > > > Receive free SQL tips - register at www.ciquery.com/sqlserver.htm
> > > > SQL Server Performance Audit - check www.ciquery.com/sqlserver_audit.htm
> > > > New article by Jack Vamvas - SQL and Markov Chains -
> > > > www.ciquery.com/articles/art_04.asp
> > > > "Andy" <Andy@.discussions.microsoft.com> wrote in message
> > > > news:AA513080-F72F-4386-93CA-93CEF0673F76@.microsoft.com...
> > > > > I am getting an error in my DTS logs about a bad page. Here is the exact
> > > > > message.
> > > > >
> > > > > Step Error Description:I/O error (bad page ID) detected during read at
> > > > > offset 0x0000022a040000 in file 'E:\SQLData\ALS_Stage_Data.MDF'.
> > > > >
> > > > > We are getting this error on 2 different servers. The process has been
> > > > > running like a champ for years and now we are getting this message. All
> > > > that
> > > > > is running when it errors out is an update statement that is joining 2
> > > > > tables. I have read some about tempdb running into these issues and it
> > > > > suggests that there may be hardware issues. That is not the case as we
> > > > have
> > > > > looked into that and we have many other processes that run on these
> > > > servers.
> > > > > I have also read that service pack 4 needs to be installed. Well we moved
> > > > > our process to another server with exactly the same configuration and it
> > > > ran
> > > > > fine on there. Had anybody else ran into this? Any suggestions? All
> > > > help
> > > > > is appreciated.
> > > > >
> > > > > Thanks
> > > >
> > > >
> > > >

Backup without Data

If I wanted to create another database with the exact same structure of our
current database, MINUS the data...is there an easy/quick way to do this?
If there's an automated way to "reset" the Identity fields as well, that
would be nice, but I could do that relatively quickly.
just script the entire database out of Enterprise Manager.
(Right click on the DB and choose "all Tasks"..."Generate Script"
there are a few options you'll need to choose in the dialog (script all
objects, script database, script object level permissions, etc). after a few
tries, you'll be an old pro.
Greg Jackson
PDX, Oregon
|||> (Right click on the DB and choose "all Tasks"..."Generate Script"
> there are a few options you'll need to choose in the dialog (script all
> objects, script database, script object level permissions, etc). after a
few
> tries, you'll be an old pro.
Thanks for the help. I ran through this process and "scripted" everything.
When I looked at the *.sql file it generates, it looks like it would drop my
current database and completely erase it essentially. This isn't what I'm
looking for. I want to create a new database with the exact same structure,
but the last thing I want to do is drop our current one.
|||Use DTS...
Choose the "Copy objects and data between SQL Server databases"
Here is the key... on the next screen, uncheck "Copy Data"
"James" <letyoudown@.verizon.net> wrote in message
news:ej$kp2pdFHA.3880@.tk2msftngp13.phx.gbl...
> few
> Thanks for the help. I ran through this process and "scripted"
everything.
> When I looked at the *.sql file it generates, it looks like it would drop
my
> current database and completely erase it essentially. This isn't what I'm
> looking for. I want to create a new database with the exact same
structure,
> but the last thing I want to do is drop our current one.
>
|||Just uncheck the "drop existing" box in the script generation dialog, then
edit the db create line in the script, so it contains the new name.
"James" wrote:

> few
> Thanks for the help. I ran through this process and "scripted" everything.
> When I looked at the *.sql file it generates, it looks like it would drop my
> current database and completely erase it essentially. This isn't what I'm
> looking for. I want to create a new database with the exact same structure,
> but the last thing I want to do is drop our current one.
>
>
|||Thank you all...worked just fine. I just get nervous about doing anything
where one checked/unchecked box could cost me a ton of time restoring a
backup.
|||yes you need to be careful....
you didnt see the fine print in my first post ?
:-)
Greg Jackson
PDX, Oregon

Backup without Data

If I wanted to create another database with the exact same structure of our
current database, MINUS the data...is there an easy/quick way to do this?
If there's an automated way to "reset" the Identity fields as well, that
would be nice, but I could do that relatively quickly.just script the entire database out of Enterprise Manager.
(Right click on the DB and choose "all Tasks"..."Generate Script"
there are a few options you'll need to choose in the dialog (script all
objects, script database, script object level permissions, etc). after a few
tries, you'll be an old pro.
Greg Jackson
PDX, Oregon|||> (Right click on the DB and choose "all Tasks"..."Generate Script"
> there are a few options you'll need to choose in the dialog (script all
> objects, script database, script object level permissions, etc). after a
few
> tries, you'll be an old pro.
Thanks for the help. I ran through this process and "scripted" everything.
When I looked at the *.sql file it generates, it looks like it would drop my
current database and completely erase it essentially. This isn't what I'm
looking for. I want to create a new database with the exact same structure,
but the last thing I want to do is drop our current one.|||Use DTS...
Choose the "Copy objects and data between SQL Server databases"
Here is the key... on the next screen, uncheck "Copy Data"
"James" <letyoudown@.verizon.net> wrote in message
news:ej$kp2pdFHA.3880@.tk2msftngp13.phx.gbl...
> > (Right click on the DB and choose "all Tasks"..."Generate Script"
> >
> > there are a few options you'll need to choose in the dialog (script all
> > objects, script database, script object level permissions, etc). after a
> few
> > tries, you'll be an old pro.
> Thanks for the help. I ran through this process and "scripted"
everything.
> When I looked at the *.sql file it generates, it looks like it would drop
my
> current database and completely erase it essentially. This isn't what I'm
> looking for. I want to create a new database with the exact same
structure,
> but the last thing I want to do is drop our current one.
>|||Just uncheck the "drop existing" box in the script generation dialog, then
edit the db create line in the script, so it contains the new name.
"James" wrote:
> > (Right click on the DB and choose "all Tasks"..."Generate Script"
> >
> > there are a few options you'll need to choose in the dialog (script all
> > objects, script database, script object level permissions, etc). after a
> few
> > tries, you'll be an old pro.
> Thanks for the help. I ran through this process and "scripted" everything.
> When I looked at the *.sql file it generates, it looks like it would drop my
> current database and completely erase it essentially. This isn't what I'm
> looking for. I want to create a new database with the exact same structure,
> but the last thing I want to do is drop our current one.
>
>|||Thank you all...worked just fine. I just get nervous about doing anything
where one checked/unchecked box could cost me a ton of time restoring a
backup.|||yes you need to be careful....
you didnt see the fine print in my first post ?
:-)
Greg Jackson
PDX, Oregon

Backup without Data

If I wanted to create another database with the exact same structure of our
current database, MINUS the data...is there an easy/quick way to do this?
If there's an automated way to "reset" the Identity fields as well, that
would be nice, but I could do that relatively quickly.just script the entire database out of Enterprise Manager.
(Right click on the DB and choose "all Tasks"..."Generate Script"
there are a few options you'll need to choose in the dialog (script all
objects, script database, script object level permissions, etc). after a few
tries, you'll be an old pro.
Greg Jackson
PDX, Oregon|||> (Right click on the DB and choose "all Tasks"..."Generate Script"
> there are a few options you'll need to choose in the dialog (script all
> objects, script database, script object level permissions, etc). after a
few
> tries, you'll be an old pro.
Thanks for the help. I ran through this process and "scripted" everything.
When I looked at the *.sql file it generates, it looks like it would drop my
current database and completely erase it essentially. This isn't what I'm
looking for. I want to create a new database with the exact same structure,
but the last thing I want to do is drop our current one.|||Use DTS...
Choose the "Copy objects and data between SQL Server databases"
Here is the key... on the next screen, uncheck "Copy Data"
"James" <letyoudown@.verizon.net> wrote in message
news:ej$kp2pdFHA.3880@.tk2msftngp13.phx.gbl...
> few
> Thanks for the help. I ran through this process and "scripted"
everything.
> When I looked at the *.sql file it generates, it looks like it would drop
my
> current database and completely erase it essentially. This isn't what I'm
> looking for. I want to create a new database with the exact same
structure,
> but the last thing I want to do is drop our current one.
>|||Just uncheck the "drop existing" box in the script generation dialog, then
edit the db create line in the script, so it contains the new name.
"James" wrote:

> few
> Thanks for the help. I ran through this process and "scripted" everything
.
> When I looked at the *.sql file it generates, it looks like it would drop
my
> current database and completely erase it essentially. This isn't what I'm
> looking for. I want to create a new database with the exact same structur
e,
> but the last thing I want to do is drop our current one.
>
>|||Thank you all...worked just fine. I just get nervous about doing anything
where one checked/unchecked box could cost me a ton of time restoring a
backup.|||yes you need to be careful....
you didnt see the fine print in my first post ?
:-)
Greg Jackson
PDX, Oregon