Error report: Interactive sorting loses the image reference

I have a table using the interactive sort feature and an image on each row.
On the report server when I sort the column the images are lost and a broken
link is displayed. In the Designer preview window the images are not lost.
Anyone else share my experience, and does anyone know how to work around
this issue?
Thanks,
Steve MunLeeuwIf I switch the image to embedded then it works as expected.
Thanks,
Steve MunLeeuw
"Steve MunLeeuw" <smunson@.clearwire.net> wrote in message
news:O$osPQxtGHA.3392@.TK2MSFTNGP04.phx.gbl...
>I have a table using the interactive sort feature and an image on each row.
>On the report server when I sort the column the images are lost and a
>broken link is displayed. In the Designer preview window the images are
>not lost. Anyone else share my experience, and does anyone know how to work
>around this issue?
> Thanks,
> Steve MunLeeuw
>

Error Redirected to Script Component : Package Doesnt fail.

I have created a data flow task. In that, in a 'data conversion', if a column fails validation then that row is redirected to a script component, which in turn writes the error to a variable.

But though the error is generated and script component receives the error, package doesnt fail.

Is there any way to set the package result to failure inside the script component? I tried set 'FailPackageOnFailure' to true but doesnt work.

Any help is greatly appreciated.

Thanks,

Don

donMahya wrote:

I have created a data flow task. In that, in a 'data conversion', if a column fails validation then that row is redirected to a script component, which in turn writes the error to a variable.

But though the error is generated and script component receives the error, package doesnt fail.

Is there any way to set the package result to failure inside the script component? I tried set 'FailPackageOnFailure' to true but doesnt work.

Any help is greatly appreciated.

Thanks,

Don

You could raise an error within the script component using:

Me.Events.FireError(...) (something like that anyway)

-Jamie

|||

Sorry for the delay. Wasnt working on this part for some time.

I tried

Me.ComponentMetaData.FireError(0, "", strErrDesc, "", 0, True) - Where strErrDesc is error decription.

but still no luck

I tried setting the maxerrorcount to 0 but No Luck. Package still completes without any failure.

Any help or ideas are greatly appreciated.

Thanks,

Don

|||

You should return the failure value inside of your script main method. I do not remember the exact enumeration value but the intellisence will give it to you.

Thanks.

Error Redirected to Script Component : Package Doesnt fail.

I have created a data flow task. In that, in a 'data conversion', if a column fails validation then that row is redirected to a script component, which in turn writes the error to a variable.

But though the error is generated and script component receives the error, package doesnt fail.

Is there any way to set the package result to failure inside the script component? I tried set 'FailPackageOnFailure' to true but doesnt work.

Any help is greatly appreciated.

Thanks,

Don

donMahya wrote:

I have created a data flow task. In that, in a 'data conversion', if a column fails validation then that row is redirected to a script component, which in turn writes the error to a variable.

But though the error is generated and script component receives the error, package doesnt fail.

Is there any way to set the package result to failure inside the script component? I tried set 'FailPackageOnFailure' to true but doesnt work.

Any help is greatly appreciated.

Thanks,

Don

You could raise an error within the script component using:

Me.Events.FireError(...) (something like that anyway)

-Jamie

|||

Sorry for the delay. Wasnt working on this part for some time.

I tried

Me.ComponentMetaData.FireError(0, "", strErrDesc, "", 0, True) - Where strErrDesc is error decription.

but still no luck

I tried setting the maxerrorcount to 0 but No Luck. Package still completes without any failure.

Any help or ideas are greatly appreciated.

Thanks,

Don

|||

You should return the failure value inside of your script main method. I do not remember the exact enumeration value but the intellisence will give it to you.

Thanks.

error output is bringing too many rows with it

I've got a Derived Columns component as part of a data flow. On this I've set the error output for my columns to Redirect Row in all cases. I've set a data watcher on the error output and then ran the package.

There are several rows which I'm expecting to fail - about 3 of them. These fail but there are also another 697 which seem to have no problem. So I fixed one of the problem columns in the source data and then re-ran the package. I only updated one row in the source so this row no longer appeared in the error output, but neither did several hundred of the other rows.

Is it possible that the error output has been tripped for that one row but for some reason it sends several hundred more rows? The ids on these additional rows follow on from the erroneous row, and when I fix that row the rows following it no longer appear in the error output.

The Derived Column transform should giuve your error handling at a row level. One row that fails should not impact the following rows. This just sounds wrong, so there is either something unexpected you've missed when looking at what rows shoudl fail, or there is a bug. Can you reproduce this behaviour on a simple set of data that could be used to log a bug? Perhaps you could send me a sample package?|||

Darren - I've managed to reproduce this with a simple package which reads data from a file. Sent to you via email.

Cheers,

Nick

|||no longer a problem once upgraded to SP2. Thanks Darren.sql

error output - ignore just one column?

When configuring error output, I want everything that is good in the row to make it to the destination, and then the offending column that is causing an error to be set to NULL, and then sent to the destination as well. In addition, I want to take the offending column's data, and route it over to an error holding table. I know about the ability to redirect the whole row, but I just sort of want to redirect just that column. For example....

Have a table with 5 columns

col1 int null,

col2 int null,

col3 char(3) null,

col4 bit null,

col5 int null

My data flow loads data from a flat file and has a record that looks like this

1 5 ABC R 3

I want the row to make it to the destination as follows....

1 5 ABC NULL 3

Then the offending data needs to go over to my error table

err# errcolumn errdata errdesc

1 col4 R Could not convert "R" to bit data type

Any way to do this?

You could create a custom component, or a script component. Otherwise, you'd need to redirect the row, and use a multicast to send it to the error destination and put the row back into the main flow, after correcting the data.|||And even though you've redirected the row, you can still just operate on one column. The problem is knowing which column is in error.|||

Yes - this is the problem - the users who review the etl loads want to see: "You had invalid data in the BirthDate column". They do not want to see - "You had invalid data somewhere on record # 26".

I really want to stay inside SSIS to do these data type checks, but I'm leaning towards shoving everything into the engine & using isdate(), isnumeric(), etc. to get the flagrant data conversion stuff cleaned up. Then bring it back into SSIS to do lookups & "softer" validations. My real table (unlike my example) has 50+ columns to do checks on, and I don't want 50 branches or more in my SSIS package, all with error flows, and unions everywhere.

Is there any way of keeping this in SSI S, using the Data conversion/Derived Column transforms, and capturing column specific errors, instead of generic row errors?

|||Take a look at this post - it may have an answer for you - http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1509836&SiteID=1|||I saw that yesterday - it looked promising, but I'm relatively sure that the folks who run the servers here won't allow anything other than the Microsoft released stuff onto the servers. I'm toying with a workaround right now that hopefully will work........I'll check back in.sql

error output - ignore just one column?

When configuring error output, I want everything that is good in the row to make it to the destination, and then the offending column that is causing an error to be set to NULL, and then sent to the destination as well. In addition, I want to take the offending column's data, and route it over to an error holding table. I know about the ability to redirect the whole row, but I just sort of want to redirect just that column. For example....

Have a table with 5 columns

col1 int null,

col2 int null,

col3 char(3) null,

col4 bit null,

col5 int null

My data flow loads data from a flat file and has a record that looks like this

1 5 ABC R 3

I want the row to make it to the destination as follows....

1 5 ABC NULL 3

Then the offending data needs to go over to my error table

err# errcolumn errdata errdesc

1 col4 R Could not convert "R" to bit data type

Any way to do this?

You could create a custom component, or a script component. Otherwise, you'd need to redirect the row, and use a multicast to send it to the error destination and put the row back into the main flow, after correcting the data.|||And even though you've redirected the row, you can still just operate on one column. The problem is knowing which column is in error.|||

Yes - this is the problem - the users who review the etl loads want to see: "You had invalid data in the BirthDate column". They do not want to see - "You had invalid data somewhere on record # 26".

I really want to stay inside SSIS to do these data type checks, but I'm leaning towards shoving everything into the engine & using isdate(), isnumeric(), etc. to get the flagrant data conversion stuff cleaned up. Then bring it back into SSIS to do lookups & "softer" validations. My real table (unlike my example) has 50+ columns to do checks on, and I don't want 50 branches or more in my SSIS package, all with error flows, and unions everywhere.

Is there any way of keeping this in SSI S, using the Data conversion/Derived Column transforms, and capturing column specific errors, instead of generic row errors?

|||Take a look at this post - it may have an answer for you - http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1509836&SiteID=1|||I saw that yesterday - it looked promising, but I'm relatively sure that the folks who run the servers here won't allow anything other than the Microsoft released stuff onto the servers. I'm toying with a workaround right now that hopefully will work........I'll check back in.

Error on bcp

Hi again

Sometimes, in some files .dat, thee following error occurs:

#@. Row 1, Column 8: Invalid character value for cast specification @.#
3877 597 2.0 Manual 1C15H4 <NULL> 24590.0000 1 2 G 2.0 ATIVO US$ 2006 2006 2 <NULL>

But the columns are OK.

Somebody can help me?The error indicates that some value in the line could not be converted to the data type of the destination column. It can be due to the format of the specified value. If you post a repro script then it might be easier to tell what the problem might be.|||Hi,

Sorry.. Only today I saw your response.

So, the dat file that I use is something like this:

1;ABADIA;12*
2;ABADIA DOS DOURADOS;18*
3;ABADIANIA;16*
4;ABAETE;18*
5;ABAETETUBA;21*
6;ABAIARA;13*
7;ABAIBA;18*
8;ABAIRA;12*
9;ABARE;12*
10;ABATIA;25*
11;ABELARDO LUZ;31*
12;ABOBORA;12*
13;ABRANTES;12*
14;ABRE CAMPO;18*
15;ABREU E LIMA;23*
16;ABUNA;28*
17;ACAIACA;18*
18;ACAILANDIA;17*
19;ACAJUTIBA;12*
20;ACARA;21*

and the command line that I use is:

bcp cdiretodev5.dbo.cidade in "./loader/dat/cidade.dat" -U sa -P pwd123 -S BART\SQLEXPRESS -c -t; -r * -E -e d:\cidade.log

The table is:

table name: cidade

columns:

id_cidade numeric(10)
no_cidade varchar(50)
id_estado numeric(4)

Thanks!!!!|||Your row terminator seems incorrect. Do you have CR/LF after *? If so, you need to change the -r option to -r "*\n" or -r "*\r\n". See the Books Online topic on BCP utility for details on the options, format files etc.|||Hi,

thank you for your help.. Only now I could see.. sorry...
well, I put the option with -r "*\n", but and some lines, The bcp doesn′t generate the *, like follows:

155;237;SLX;;;R$;;1;5;;1;;;;;;;2;;;2 ou 4;0;007001-7;;*
156;237;SDX;;;R$;;1;5;;1;;;;;;;2;;;2 ou 4;0;007001-7;;*
1317;511;3.0 E;;;R$;;1;5;;1;;;;;;;2;;;2 ou 4;0;021069-2;;*
1318;511;3.0 SL;;;R$;;1;5;;1;;;;;;;2;;;2 ou 4;0;021070-6;;*
1988;46;Sedan Wind 1.0;5C19Z1;SIMP;R$;18486.0000;1;5;;1;Powertech 1.0L M.P.F.I. 4cil.;4056 mm;46 l;8,3 mkgf a 3.000 rpm;14.8 km/l;11.7 km/l;1;2000;2001;4;0;

Is there a limit for number of columns to line?

The new error now is #@. Row 1, Column 27: String data, right truncation @.#

thank you very much.|||The error message indicates that the data in column 27 or row 1 exceeds length of the destination column. So check the length of data against your table's column definition. There is a limit to the number of columns in a table in SQL Server but there is really none in the data file. As long as you have to terminators defined properly BCP should be able to parse the file correctly assuming it is formatted correctly.

Error on bcp

Hi again

Sometimes, in some files .dat, thee following error occurs:

#@. Row 1, Column 8: Invalid character value for cast specification @.#
3877 597 2.0 Manual 1C15H4 <NULL> 24590.0000 1 2 G 2.0 ATIVO US$ 2006 2006 2 <NULL>

But the columns are OK.

Somebody can help me?The error indicates that some value in the line could not be converted to the data type of the destination column. It can be due to the format of the specified value. If you post a repro script then it might be easier to tell what the problem might be.|||Hi,

Sorry.. Only today I saw your response.

So, the dat file that I use is something like this:

1;ABADIA;12*
2;ABADIA DOS DOURADOS;18*
3;ABADIANIA;16*
4;ABAETE;18*
5;ABAETETUBA;21*
6;ABAIARA;13*
7;ABAIBA;18*
8;ABAIRA;12*
9;ABARE;12*
10;ABATIA;25*
11;ABELARDO LUZ;31*
12;ABOBORA;12*
13;ABRANTES;12*
14;ABRE CAMPO;18*
15;ABREU E LIMA;23*
16;ABUNA;28*
17;ACAIACA;18*
18;ACAILANDIA;17*
19;ACAJUTIBA;12*
20;ACARA;21*

and the command line that I use is:

bcp cdiretodev5.dbo.cidade in "./loader/dat/cidade.dat" -U sa -P pwd123 -S BART\SQLEXPRESS -c -t; -r * -E -e d:\cidade.log

The table is:

table name: cidade

columns:

id_cidade numeric(10)
no_cidade varchar(50)
id_estado numeric(4)

Thanks!!!!|||Your row terminator seems incorrect. Do you have CR/LF after *? If so, you need to change the -r option to -r "*\n" or -r "*\r\n". See the Books Online topic on BCP utility for details on the options, format files etc.|||Hi,

thank you for your help.. Only now I could see.. sorry...
well, I put the option with -r "*\n", but and some lines, The bcp doesn′t generate the *, like follows:

155;237;SLX;;;R$;;1;5;;1;;;;;;;2;;;2 ou 4;0;007001-7;;*
156;237;SDX;;;R$;;1;5;;1;;;;;;;2;;;2 ou 4;0;007001-7;;*
1317;511;3.0 E;;;R$;;1;5;;1;;;;;;;2;;;2 ou 4;0;021069-2;;*
1318;511;3.0 SL;;;R$;;1;5;;1;;;;;;;2;;;2 ou 4;0;021070-6;;*
1988;46;Sedan Wind 1.0;5C19Z1;SIMP;R$;18486.0000;1;5;;1;Powertech 1.0L M.P.F.I. 4cil.;4056 mm;46 l;8,3 mkgf a 3.000 rpm;14.8 km/l;11.7 km/l;1;2000;2001;4;0;

Is there a limit for number of columns to line?

The new error now is #@. Row 1, Column 27: String data, right truncation @.#

thank you very much.|||The error message indicates that the data in column 27 or row 1 exceeds length of the destination column. So check the length of data against your table's column definition. There is a limit to the number of columns in a table in SQL Server but there is really none in the data file. As long as you have to terminators defined properly BCP should be able to parse the file correctly assuming it is formatted correctly.

Error on Attaching Database

When attaching a database that was detached from another SQL Server instance.

I got the error message below:

Error 602: Could not find row in sysindexes for database ID 25, object ID 1,
index ID 1. Run DBCC CHECKTABLE on sysindexes.

i am using SQL Server 2000

Thanks and Regards

Was the database you attached from a SQL Server 2005 server? I get that error if I attach a 2005 database to a 2000 SQL Server.

I don't know at this time thought if we are suppose to be able to attach a SQL 2005 database to a SQL 2000 server even if we keep it compatable.|||I also get this error when detaching a database from SQL Server 2005 and attaching to SQL Server 2000. Not sure what Microsoft's recommendation is or how to determine what might have changed in the schema to make it no longer compatible with SQL Server 2000.|||

I just hope somebody would help solve this prob coz i do have the same prob.

I can't attach a database from sql2005 back to sql2000 and it's giving me a lot of headache!

I got loads of work to do and this prob is eating my time.

Help!

|||You can't attach a 2005 database to 2000. The best you can do here is to export the data from the 2005 database and import into a 2000 database.|||It's not possible to take a sql2k5 database and attach it to sql2k. The meta data has changed drasticly on sql2k5. The change cannot be understood by sql2k.

Your only option is to export/import to transfer data between the versions.|||You cannot attach a SQL Server 2005 database to SQL Server 2000 - even if this used to be a SQL Server 2000 database attached to SQL Server 2005 and attaching it back to SQL Server 2000. SQL Server 2005 changes some system objects which SQL Server 2000 does not have.|||If this is the case what is the reason for the compatability level. When I run sp_dbcmptlevel 'database' I get an 80, after I have made changes to the database with 2005 (80 is 2000, 90 is 2005). I was under the impression from a Microsoft person that this was something that could be done. I would like to do this incase we have major problems in Production after the upgrade to 2005. I have a lot of data in 50+ tables. import/Export would not be a good solution. Anyone from Microsoft care to chime in.|||Database compatibility has little to do with the changes in meta data. dbcmptlevel is set to allow sql2k5 to run the database at the current or lower settings.

This issue is very much not isolated. It's the same if you take a Mpeg4 file and try to play it with a Mpeg2 player. It just doesn't work.|||

I think upward compatibility doesn't work.

|||Why would you be passing around databases between in sql2000 and sql2005 in the first place? Detaching, moving, and attaching a database is a fairly rare occurrence to us.|||

JonM wrote:

Why would you be passing around databases between in sql2000 and sql2005 in the first place? Detaching, moving, and attaching a database is a fairly rare occurrence to us.

Jon,

With all due respect, what's it matter the reason for doing so? Whether it's a rare occurance or not, it's still a known issue that obviously many people have a problem with.

Now, you asked for a reason, so here's my scenerio.

I had a database driven website designed by an outside company, to be hosted by myself internally. The company that designed the site designed the DB in 2005 while I have SQL 2000.

Do you have any comments or resolution that may be of assistance to me / us?

Thank you.

Chris

|||

reason 1

because the host provider has stated there is a problem with your database. You do not have a local copy. They take you off line and tell you to fix it and send you a 2005 mbf file.....You only have sql 2003

|||

It sounds like you mainly want to perform maintenance or troubleshoot your sql server 2005 database and then send it back to your webhost that will run in it production. With this in mind I would recommend the following options:

1. Download the SQL Server 2005 Express Edition with Advanced Tools.

It includes the sql management studio which you can use to attach, detach, and manipulate your sql 2005 databases.

2. Buy a copy of SQL Server 2005 Developer Edition

This is a fairly cheap version of SQL Server and it has the functionality of enterprise edition. It is perfect for developing, troubleshooting and testing. It is also available in most MSDN Subscription levels. However, if you are only using the OLTP databse (which many of us are), I would simply recommend Express Edition.

3. Ask your webdesigner to migrate it to SQL Server 2000

If SQL 2000 is a design requirement, ask them if they could convert it over for you. It should not be that difficult, unless we are talking about a massive web application with hundreds of stored procedures.

|||

I've loaded the sql server 2005 express, I do have the sql 2005 server but I have to figure out how to run install with a script as I have 2000 on my machine.....

I can not figure out how to run a maintenance using this express version to save my life....Is anyone willing to give me a hand? I sure would apprieciate it.

Error on Attaching Database

When attaching a database that was detached from another SQL Server instance.

I got the error message below:

Error 602: Could not find row in sysindexes for database ID 25, object ID 1,
index ID 1. Run DBCC CHECKTABLE on sysindexes.

i am using SQL Server 2000

Thanks and Regards

Was the database you attached from a SQL Server 2005 server? I get that error if I attach a 2005 database to a 2000 SQL Server.

I don't know at this time thought if we are suppose to be able to attach a SQL 2005 database to a SQL 2000 server even if we keep it compatable.|||I also get this error when detaching a database from SQL Server 2005 and attaching to SQL Server 2000. Not sure what Microsoft's recommendation is or how to determine what might have changed in the schema to make it no longer compatible with SQL Server 2000.|||

I just hope somebody would help solve this prob coz i do have the same prob.

I can't attach a database from sql2005 back to sql2000 and it's giving me a lot of headache!

I got loads of work to do and this prob is eating my time.

Help!

|||You can't attach a 2005 database to 2000. The best you can do here is to export the data from the 2005 database and import into a 2000 database.|||It's not possible to take a sql2k5 database and attach it to sql2k. The meta data has changed drasticly on sql2k5. The change cannot be understood by sql2k.

Your only option is to export/import to transfer data between the versions.|||You cannot attach a SQL Server 2005 database to SQL Server 2000 - even if this used to be a SQL Server 2000 database attached to SQL Server 2005 and attaching it back to SQL Server 2000. SQL Server 2005 changes some system objects which SQL Server 2000 does not have.|||If this is the case what is the reason for the compatability level. When I run sp_dbcmptlevel 'database' I get an 80, after I have made changes to the database with 2005 (80 is 2000, 90 is 2005). I was under the impression from a Microsoft person that this was something that could be done. I would like to do this incase we have major problems in Production after the upgrade to 2005. I have a lot of data in 50+ tables. import/Export would not be a good solution. Anyone from Microsoft care to chime in.|||Database compatibility has little to do with the changes in meta data. dbcmptlevel is set to allow sql2k5 to run the database at the current or lower settings.

This issue is very much not isolated. It's the same if you take a Mpeg4 file and try to play it with a Mpeg2 player. It just doesn't work.|||

I think upward compatibility doesn't work.

|||Why would you be passing around databases between in sql2000 and sql2005 in the first place? Detaching, moving, and attaching a database is a fairly rare occurrence to us.|||

JonM wrote:

Why would you be passing around databases between in sql2000 and sql2005 in the first place? Detaching, moving, and attaching a database is a fairly rare occurrence to us.

Jon,

With all due respect, what's it matter the reason for doing so? Whether it's a rare occurance or not, it's still a known issue that obviously many people have a problem with.

Now, you asked for a reason, so here's my scenerio.

I had a database driven website designed by an outside company, to be hosted by myself internally. The company that designed the site designed the DB in 2005 while I have SQL 2000.

Do you have any comments or resolution that may be of assistance to me / us?

Thank you.

Chris

|||

reason 1

because the host provider has stated there is a problem with your database. You do not have a local copy. They take you off line and tell you to fix it and send you a 2005 mbf file.....You only have sql 2003

|||

It sounds like you mainly want to perform maintenance or troubleshoot your sql server 2005 database and then send it back to your webhost that will run in it production. With this in mind I would recommend the following options:

1. Download the SQL Server 2005 Express Edition with Advanced Tools.

It includes the sql management studio which you can use to attach, detach, and manipulate your sql 2005 databases.

2. Buy a copy of SQL Server 2005 Developer Edition

This is a fairly cheap version of SQL Server and it has the functionality of enterprise edition. It is perfect for developing, troubleshooting and testing. It is also available in most MSDN Subscription levels. However, if you are only using the OLTP databse (which many of us are), I would simply recommend Express Edition.

3. Ask your webdesigner to migrate it to SQL Server 2000

If SQL 2000 is a design requirement, ask them if they could convert it over for you. It should not be that difficult, unless we are talking about a massive web application with hundreds of stored procedures.

|||

I've loaded the sql server 2005 express, I do have the sql 2005 server but I have to figure out how to run install with a script as I have 2000 on my machine.....

I can not figure out how to run a maintenance using this express version to save my life....Is anyone willing to give me a hand? I sure would apprieciate it.

Error on Attaching Database

When attaching a database that was detached from another SQL Server instance.

I got the error message below:

Error 602: Could not find row in sysindexes for database ID 25, object ID 1,
index ID 1. Run DBCC CHECKTABLE on sysindexes.

i am using SQL Server 2000

Thanks and Regards

Was the database you attached from a SQL Server 2005 server? I get that error if I attach a 2005 database to a 2000 SQL Server.

I don't know at this time thought if we are suppose to be able to attach a SQL 2005 database to a SQL 2000 server even if we keep it compatable.|||I also get this error when detaching a database from SQL Server 2005 and attaching to SQL Server 2000. Not sure what Microsoft's recommendation is or how to determine what might have changed in the schema to make it no longer compatible with SQL Server 2000.|||

I just hope somebody would help solve this prob coz i do have the same prob.

I can't attach a database from sql2005 back to sql2000 and it's giving me a lot of headache!

I got loads of work to do and this prob is eating my time.

Help!

|||You can't attach a 2005 database to 2000. The best you can do here is to export the data from the 2005 database and import into a 2000 database.|||It's not possible to take a sql2k5 database and attach it to sql2k. The meta data has changed drasticly on sql2k5. The change cannot be understood by sql2k.

Your only option is to export/import to transfer data between the versions.|||You cannot attach a SQL Server 2005 database to SQL Server 2000 - even if this used to be a SQL Server 2000 database attached to SQL Server 2005 and attaching it back to SQL Server 2000. SQL Server 2005 changes some system objects which SQL Server 2000 does not have.|||If this is the case what is the reason for the compatability level. When I run sp_dbcmptlevel 'database' I get an 80, after I have made changes to the database with 2005 (80 is 2000, 90 is 2005). I was under the impression from a Microsoft person that this was something that could be done. I would like to do this incase we have major problems in Production after the upgrade to 2005. I have a lot of data in 50+ tables. import/Export would not be a good solution. Anyone from Microsoft care to chime in.|||Database compatibility has little to do with the changes in meta data. dbcmptlevel is set to allow sql2k5 to run the database at the current or lower settings.

This issue is very much not isolated. It's the same if you take a Mpeg4 file and try to play it with a Mpeg2 player. It just doesn't work.|||

I think upward compatibility doesn't work.

|||Why would you be passing around databases between in sql2000 and sql2005 in the first place? Detaching, moving, and attaching a database is a fairly rare occurrence to us.|||

JonM wrote:

Why would you be passing around databases between in sql2000 and sql2005 in the first place? Detaching, moving, and attaching a database is a fairly rare occurrence to us.

Jon,

With all due respect, what's it matter the reason for doing so? Whether it's a rare occurance or not, it's still a known issue that obviously many people have a problem with.

Now, you asked for a reason, so here's my scenerio.

I had a database driven website designed by an outside company, to be hosted by myself internally. The company that designed the site designed the DB in 2005 while I have SQL 2000.

Do you have any comments or resolution that may be of assistance to me / us?

Thank you.

Chris

|||

reason 1

because the host provider has stated there is a problem with your database. You do not have a local copy. They take you off line and tell you to fix it and send you a 2005 mbf file.....You only have sql 2003

|||

It sounds like you mainly want to perform maintenance or troubleshoot your sql server 2005 database and then send it back to your webhost that will run in it production. With this in mind I would recommend the following options:

1. Download the SQL Server 2005 Express Edition with Advanced Tools.

It includes the sql management studio which you can use to attach, detach, and manipulate your sql 2005 databases.

2. Buy a copy of SQL Server 2005 Developer Edition

This is a fairly cheap version of SQL Server and it has the functionality of enterprise edition. It is perfect for developing, troubleshooting and testing. It is also available in most MSDN Subscription levels. However, if you are only using the OLTP databse (which many of us are), I would simply recommend Express Edition.

3. Ask your webdesigner to migrate it to SQL Server 2000

If SQL 2000 is a design requirement, ask them if they could convert it over for you. It should not be that difficult, unless we are talking about a massive web application with hundreds of stored procedures.

|||

I've loaded the sql server 2005 express, I do have the sql 2005 server but I have to figure out how to run install with a script as I have 2000 on my machine.....

I can not figure out how to run a maintenance using this express version to save my life....Is anyone willing to give me a hand? I sure would apprieciate it.

Error on Attaching Database

When attaching a database that was detached from another SQL Server instance.

I got the error message below:

Error 602: Could not find row in sysindexes for database ID 25, object ID 1,
index ID 1. Run DBCC CHECKTABLE on sysindexes.

i am using SQL Server 2000

Thanks and Regards

Was the database you attached from a SQL Server 2005 server? I get that error if I attach a 2005 database to a 2000 SQL Server.

I don't know at this time thought if we are suppose to be able to attach a SQL 2005 database to a SQL 2000 server even if we keep it compatable.|||I also get this error when detaching a database from SQL Server 2005 and attaching to SQL Server 2000. Not sure what Microsoft's recommendation is or how to determine what might have changed in the schema to make it no longer compatible with SQL Server 2000.|||

I just hope somebody would help solve this prob coz i do have the same prob.

I can't attach a database from sql2005 back to sql2000 and it's giving me a lot of headache!

I got loads of work to do and this prob is eating my time.

Help!

|||You can't attach a 2005 database to 2000. The best you can do here is to export the data from the 2005 database and import into a 2000 database.|||It's not possible to take a sql2k5 database and attach it to sql2k. The meta data has changed drasticly on sql2k5. The change cannot be understood by sql2k.

Your only option is to export/import to transfer data between the versions.|||You cannot attach a SQL Server 2005 database to SQL Server 2000 - even if this used to be a SQL Server 2000 database attached to SQL Server 2005 and attaching it back to SQL Server 2000. SQL Server 2005 changes some system objects which SQL Server 2000 does not have.|||If this is the case what is the reason for the compatability level. When I run sp_dbcmptlevel 'database' I get an 80, after I have made changes to the database with 2005 (80 is 2000, 90 is 2005). I was under the impression from a Microsoft person that this was something that could be done. I would like to do this incase we have major problems in Production after the upgrade to 2005. I have a lot of data in 50+ tables. import/Export would not be a good solution. Anyone from Microsoft care to chime in.|||Database compatibility has little to do with the changes in meta data. dbcmptlevel is set to allow sql2k5 to run the database at the current or lower settings.

This issue is very much not isolated. It's the same if you take a Mpeg4 file and try to play it with a Mpeg2 player. It just doesn't work.|||

I think upward compatibility doesn't work.

|||Why would you be passing around databases between in sql2000 and sql2005 in the first place? Detaching, moving, and attaching a database is a fairly rare occurrence to us.|||

JonM wrote:

Why would you be passing around databases between in sql2000 and sql2005 in the first place? Detaching, moving, and attaching a database is a fairly rare occurrence to us.

Jon,

With all due respect, what's it matter the reason for doing so? Whether it's a rare occurance or not, it's still a known issue that obviously many people have a problem with.

Now, you asked for a reason, so here's my scenerio.

I had a database driven website designed by an outside company, to be hosted by myself internally. The company that designed the site designed the DB in 2005 while I have SQL 2000.

Do you have any comments or resolution that may be of assistance to me / us?

Thank you.

Chris

|||

reason 1

because the host provider has stated there is a problem with your database. You do not have a local copy. They take you off line and tell you to fix it and send you a 2005 mbf file.....You only have sql 2003

|||

It sounds like you mainly want to perform maintenance or troubleshoot your sql server 2005 database and then send it back to your webhost that will run in it production. With this in mind I would recommend the following options:

1. Download the SQL Server 2005 Express Edition with Advanced Tools.

It includes the sql management studio which you can use to attach, detach, and manipulate your sql 2005 databases.

2. Buy a copy of SQL Server 2005 Developer Edition

This is a fairly cheap version of SQL Server and it has the functionality of enterprise edition. It is perfect for developing, troubleshooting and testing. It is also available in most MSDN Subscription levels. However, if you are only using the OLTP databse (which many of us are), I would simply recommend Express Edition.

3. Ask your webdesigner to migrate it to SQL Server 2000

If SQL 2000 is a design requirement, ask them if they could convert it over for you. It should not be that difficult, unless we are talking about a massive web application with hundreds of stored procedures.

|||

I've loaded the sql server 2005 express, I do have the sql 2005 server but I have to figure out how to run install with a script as I have 2000 on my machine.....

I can not figure out how to run a maintenance using this express version to save my life....Is anyone willing to give me a hand? I sure would apprieciate it.

Error on Attaching Database

When attaching a database that was detached from another SQL Server instance.

I got the error message below:

Error 602: Could not find row in sysindexes for database ID 25, object ID 1,
index ID 1. Run DBCC CHECKTABLE on sysindexes.

i am using SQL Server 2000

Thanks and Regards

Was the database you attached from a SQL Server 2005 server? I get that error if I attach a 2005 database to a 2000 SQL Server.

I don't know at this time thought if we are suppose to be able to attach a SQL 2005 database to a SQL 2000 server even if we keep it compatable.|||I also get this error when detaching a database from SQL Server 2005 and attaching to SQL Server 2000. Not sure what Microsoft's recommendation is or how to determine what might have changed in the schema to make it no longer compatible with SQL Server 2000.|||

I just hope somebody would help solve this prob coz i do have the same prob.

I can't attach a database from sql2005 back to sql2000 and it's giving me a lot of headache!

I got loads of work to do and this prob is eating my time.

Help!

|||You can't attach a 2005 database to 2000. The best you can do here is to export the data from the 2005 database and import into a 2000 database.|||It's not possible to take a sql2k5 database and attach it to sql2k. The meta data has changed drasticly on sql2k5. The change cannot be understood by sql2k.

Your only option is to export/import to transfer data between the versions.|||You cannot attach a SQL Server 2005 database to SQL Server 2000 - even if this used to be a SQL Server 2000 database attached to SQL Server 2005 and attaching it back to SQL Server 2000. SQL Server 2005 changes some system objects which SQL Server 2000 does not have.|||If this is the case what is the reason for the compatability level. When I run sp_dbcmptlevel 'database' I get an 80, after I have made changes to the database with 2005 (80 is 2000, 90 is 2005). I was under the impression from a Microsoft person that this was something that could be done. I would like to do this incase we have major problems in Production after the upgrade to 2005. I have a lot of data in 50+ tables. import/Export would not be a good solution. Anyone from Microsoft care to chime in.|||Database compatibility has little to do with the changes in meta data. dbcmptlevel is set to allow sql2k5 to run the database at the current or lower settings.

This issue is very much not isolated. It's the same if you take a Mpeg4 file and try to play it with a Mpeg2 player. It just doesn't work.|||

I think upward compatibility doesn't work.

|||Why would you be passing around databases between in sql2000 and sql2005 in the first place? Detaching, moving, and attaching a database is a fairly rare occurrence to us.|||

JonM wrote:

Why would you be passing around databases between in sql2000 and sql2005 in the first place? Detaching, moving, and attaching a database is a fairly rare occurrence to us.

Jon,

With all due respect, what's it matter the reason for doing so? Whether it's a rare occurance or not, it's still a known issue that obviously many people have a problem with.

Now, you asked for a reason, so here's my scenerio.

I had a database driven website designed by an outside company, to be hosted by myself internally. The company that designed the site designed the DB in 2005 while I have SQL 2000.

Do you have any comments or resolution that may be of assistance to me / us?

Thank you.

Chris

|||

reason 1

because the host provider has stated there is a problem with your database. You do not have a local copy. They take you off line and tell you to fix it and send you a 2005 mbf file.....You only have sql 2003

|||

It sounds like you mainly want to perform maintenance or troubleshoot your sql server 2005 database and then send it back to your webhost that will run in it production. With this in mind I would recommend the following options:

1. Download the SQL Server 2005 Express Edition with Advanced Tools.

It includes the sql management studio which you can use to attach, detach, and manipulate your sql 2005 databases.

2. Buy a copy of SQL Server 2005 Developer Edition

This is a fairly cheap version of SQL Server and it has the functionality of enterprise edition. It is perfect for developing, troubleshooting and testing. It is also available in most MSDN Subscription levels. However, if you are only using the OLTP databse (which many of us are), I would simply recommend Express Edition.

3. Ask your webdesigner to migrate it to SQL Server 2000

If SQL 2000 is a design requirement, ask them if they could convert it over for you. It should not be that difficult, unless we are talking about a massive web application with hundreds of stored procedures.

|||

I've loaded the sql server 2005 express, I do have the sql 2005 server but I have to figure out how to run install with a script as I have 2000 on my machine.....

I can not figure out how to run a maintenance using this express version to save my life....Is anyone willing to give me a hand? I sure would apprieciate it.

Error on Attaching Database

When attaching a database that was detached from another SQL Server instance.

I got the error message below:

Error 602: Could not find row in sysindexes for database ID 25, object ID 1,
index ID 1. Run DBCC CHECKTABLE on sysindexes.

i am using SQL Server 2000

Thanks and Regards

Was the database you attached from a SQL Server 2005 server? I get that error if I attach a 2005 database to a 2000 SQL Server.

I don't know at this time thought if we are suppose to be able to attach a SQL 2005 database to a SQL 2000 server even if we keep it compatable.|||I also get this error when detaching a database from SQL Server 2005 and attaching to SQL Server 2000. Not sure what Microsoft's recommendation is or how to determine what might have changed in the schema to make it no longer compatible with SQL Server 2000.|||

I just hope somebody would help solve this prob coz i do have the same prob.

I can't attach a database from sql2005 back to sql2000 and it's giving me a lot of headache!

I got loads of work to do and this prob is eating my time.

Help!

|||You can't attach a 2005 database to 2000. The best you can do here is to export the data from the 2005 database and import into a 2000 database.|||It's not possible to take a sql2k5 database and attach it to sql2k. The meta data has changed drasticly on sql2k5. The change cannot be understood by sql2k.

Your only option is to export/import to transfer data between the versions.|||You cannot attach a SQL Server 2005 database to SQL Server 2000 - even if this used to be a SQL Server 2000 database attached to SQL Server 2005 and attaching it back to SQL Server 2000. SQL Server 2005 changes some system objects which SQL Server 2000 does not have.|||If this is the case what is the reason for the compatability level. When I run sp_dbcmptlevel 'database' I get an 80, after I have made changes to the database with 2005 (80 is 2000, 90 is 2005). I was under the impression from a Microsoft person that this was something that could be done. I would like to do this incase we have major problems in Production after the upgrade to 2005. I have a lot of data in 50+ tables. import/Export would not be a good solution. Anyone from Microsoft care to chime in.|||Database compatibility has little to do with the changes in meta data. dbcmptlevel is set to allow sql2k5 to run the database at the current or lower settings.

This issue is very much not isolated. It's the same if you take a Mpeg4 file and try to play it with a Mpeg2 player. It just doesn't work.|||

I think upward compatibility doesn't work.

|||Why would you be passing around databases between in sql2000 and sql2005 in the first place? Detaching, moving, and attaching a database is a fairly rare occurrence to us.|||

JonM wrote:

Why would you be passing around databases between in sql2000 and sql2005 in the first place? Detaching, moving, and attaching a database is a fairly rare occurrence to us.

Jon,

With all due respect, what's it matter the reason for doing so? Whether it's a rare occurance or not, it's still a known issue that obviously many people have a problem with.

Now, you asked for a reason, so here's my scenerio.

I had a database driven website designed by an outside company, to be hosted by myself internally. The company that designed the site designed the DB in 2005 while I have SQL 2000.

Do you have any comments or resolution that may be of assistance to me / us?

Thank you.

Chris

|||

reason 1

because the host provider has stated there is a problem with your database. You do not have a local copy. They take you off line and tell you to fix it and send you a 2005 mbf file.....You only have sql 2003

|||

It sounds like you mainly want to perform maintenance or troubleshoot your sql server 2005 database and then send it back to your webhost that will run in it production. With this in mind I would recommend the following options:

1. Download the SQL Server 2005 Express Edition with Advanced Tools.

It includes the sql management studio which you can use to attach, detach, and manipulate your sql 2005 databases.

2. Buy a copy of SQL Server 2005 Developer Edition

This is a fairly cheap version of SQL Server and it has the functionality of enterprise edition. It is perfect for developing, troubleshooting and testing. It is also available in most MSDN Subscription levels. However, if you are only using the OLTP databse (which many of us are), I would simply recommend Express Edition.

3. Ask your webdesigner to migrate it to SQL Server 2000

If SQL 2000 is a design requirement, ask them if they could convert it over for you. It should not be that difficult, unless we are talking about a massive web application with hundreds of stored procedures.

|||

I've loaded the sql server 2005 express, I do have the sql 2005 server but I have to figure out how to run install with a script as I have 2000 on my machine.....

I can not figure out how to run a maintenance using this express version to save my life....Is anyone willing to give me a hand? I sure would apprieciate it.

Error on Attaching Database

When attaching a database that was detached from another SQL Server instance.

I got the error message below:

Error 602: Could not find row in sysindexes for database ID 25, object ID 1,
index ID 1. Run DBCC CHECKTABLE on sysindexes.

i am using SQL Server 2000

Thanks and Regards

Was the database you attached from a SQL Server 2005 server? I get that error if I attach a 2005 database to a 2000 SQL Server.

I don't know at this time thought if we are suppose to be able to attach a SQL 2005 database to a SQL 2000 server even if we keep it compatable.|||I also get this error when detaching a database from SQL Server 2005 and attaching to SQL Server 2000. Not sure what Microsoft's recommendation is or how to determine what might have changed in the schema to make it no longer compatible with SQL Server 2000.|||

I just hope somebody would help solve this prob coz i do have the same prob.

I can't attach a database from sql2005 back to sql2000 and it's giving me a lot of headache!

I got loads of work to do and this prob is eating my time.

Help!

|||You can't attach a 2005 database to 2000. The best you can do here is to export the data from the 2005 database and import into a 2000 database.|||It's not possible to take a sql2k5 database and attach it to sql2k. The meta data has changed drasticly on sql2k5. The change cannot be understood by sql2k.

Your only option is to export/import to transfer data between the versions.|||You cannot attach a SQL Server 2005 database to SQL Server 2000 - even if this used to be a SQL Server 2000 database attached to SQL Server 2005 and attaching it back to SQL Server 2000. SQL Server 2005 changes some system objects which SQL Server 2000 does not have.|||If this is the case what is the reason for the compatability level. When I run sp_dbcmptlevel 'database' I get an 80, after I have made changes to the database with 2005 (80 is 2000, 90 is 2005). I was under the impression from a Microsoft person that this was something that could be done. I would like to do this incase we have major problems in Production after the upgrade to 2005. I have a lot of data in 50+ tables. import/Export would not be a good solution. Anyone from Microsoft care to chime in.|||Database compatibility has little to do with the changes in meta data. dbcmptlevel is set to allow sql2k5 to run the database at the current or lower settings.

This issue is very much not isolated. It's the same if you take a Mpeg4 file and try to play it with a Mpeg2 player. It just doesn't work.|||

I think upward compatibility doesn't work.

|||Why would you be passing around databases between in sql2000 and sql2005 in the first place? Detaching, moving, and attaching a database is a fairly rare occurrence to us.|||

JonM wrote:

Why would you be passing around databases between in sql2000 and sql2005 in the first place? Detaching, moving, and attaching a database is a fairly rare occurrence to us.

Jon,

With all due respect, what's it matter the reason for doing so? Whether it's a rare occurance or not, it's still a known issue that obviously many people have a problem with.

Now, you asked for a reason, so here's my scenerio.

I had a database driven website designed by an outside company, to be hosted by myself internally. The company that designed the site designed the DB in 2005 while I have SQL 2000.

Do you have any comments or resolution that may be of assistance to me / us?

Thank you.

Chris

|||

reason 1

because the host provider has stated there is a problem with your database. You do not have a local copy. They take you off line and tell you to fix it and send you a 2005 mbf file.....You only have sql 2003

|||

It sounds like you mainly want to perform maintenance or troubleshoot your sql server 2005 database and then send it back to your webhost that will run in it production. With this in mind I would recommend the following options:

1. Download the SQL Server 2005 Express Edition with Advanced Tools.

It includes the sql management studio which you can use to attach, detach, and manipulate your sql 2005 databases.

2. Buy a copy of SQL Server 2005 Developer Edition

This is a fairly cheap version of SQL Server and it has the functionality of enterprise edition. It is perfect for developing, troubleshooting and testing. It is also available in most MSDN Subscription levels. However, if you are only using the OLTP databse (which many of us are), I would simply recommend Express Edition.

3. Ask your webdesigner to migrate it to SQL Server 2000

If SQL 2000 is a design requirement, ask them if they could convert it over for you. It should not be that difficult, unless we are talking about a massive web application with hundreds of stored procedures.

|||

I've loaded the sql server 2005 express, I do have the sql 2005 server but I have to figure out how to run install with a script as I have 2000 on my machine.....

I can not figure out how to run a maintenance using this express version to save my life....Is anyone willing to give me a hand? I sure would apprieciate it.

Error on Attaching Database

When attaching a database that was detached from another SQL Server instance.

I got the error message below:

Error 602: Could not find row in sysindexes for database ID 25, object ID 1,
index ID 1. Run DBCC CHECKTABLE on sysindexes.

i am using SQL Server 2000

Thanks and Regards

Was the database you attached from a SQL Server 2005 server? I get that error if I attach a 2005 database to a 2000 SQL Server.

I don't know at this time thought if we are suppose to be able to attach a SQL 2005 database to a SQL 2000 server even if we keep it compatable.|||I also get this error when detaching a database from SQL Server 2005 and attaching to SQL Server 2000. Not sure what Microsoft's recommendation is or how to determine what might have changed in the schema to make it no longer compatible with SQL Server 2000.|||

I just hope somebody would help solve this prob coz i do have the same prob.

I can't attach a database from sql2005 back to sql2000 and it's giving me a lot of headache!

I got loads of work to do and this prob is eating my time.

Help!

|||You can't attach a 2005 database to 2000. The best you can do here is to export the data from the 2005 database and import into a 2000 database.|||It's not possible to take a sql2k5 database and attach it to sql2k. The meta data has changed drasticly on sql2k5. The change cannot be understood by sql2k.

Your only option is to export/import to transfer data between the versions.|||You cannot attach a SQL Server 2005 database to SQL Server 2000 - even if this used to be a SQL Server 2000 database attached to SQL Server 2005 and attaching it back to SQL Server 2000. SQL Server 2005 changes some system objects which SQL Server 2000 does not have.|||If this is the case what is the reason for the compatability level. When I run sp_dbcmptlevel 'database' I get an 80, after I have made changes to the database with 2005 (80 is 2000, 90 is 2005). I was under the impression from a Microsoft person that this was something that could be done. I would like to do this incase we have major problems in Production after the upgrade to 2005. I have a lot of data in 50+ tables. import/Export would not be a good solution. Anyone from Microsoft care to chime in.|||Database compatibility has little to do with the changes in meta data. dbcmptlevel is set to allow sql2k5 to run the database at the current or lower settings.

This issue is very much not isolated. It's the same if you take a Mpeg4 file and try to play it with a Mpeg2 player. It just doesn't work.|||

I think upward compatibility doesn't work.

|||Why would you be passing around databases between in sql2000 and sql2005 in the first place? Detaching, moving, and attaching a database is a fairly rare occurrence to us.|||

JonM wrote:

Why would you be passing around databases between in sql2000 and sql2005 in the first place? Detaching, moving, and attaching a database is a fairly rare occurrence to us.

Jon,

With all due respect, what's it matter the reason for doing so? Whether it's a rare occurance or not, it's still a known issue that obviously many people have a problem with.

Now, you asked for a reason, so here's my scenerio.

I had a database driven website designed by an outside company, to be hosted by myself internally. The company that designed the site designed the DB in 2005 while I have SQL 2000.

Do you have any comments or resolution that may be of assistance to me / us?

Thank you.

Chris

|||

reason 1

because the host provider has stated there is a problem with your database. You do not have a local copy. They take you off line and tell you to fix it and send you a 2005 mbf file.....You only have sql 2003

|||

It sounds like you mainly want to perform maintenance or troubleshoot your sql server 2005 database and then send it back to your webhost that will run in it production. With this in mind I would recommend the following options:

1. Download the SQL Server 2005 Express Edition with Advanced Tools.

It includes the sql management studio which you can use to attach, detach, and manipulate your sql 2005 databases.

2. Buy a copy of SQL Server 2005 Developer Edition

This is a fairly cheap version of SQL Server and it has the functionality of enterprise edition. It is perfect for developing, troubleshooting and testing. It is also available in most MSDN Subscription levels. However, if you are only using the OLTP databse (which many of us are), I would simply recommend Express Edition.

3. Ask your webdesigner to migrate it to SQL Server 2000

If SQL 2000 is a design requirement, ask them if they could convert it over for you. It should not be that difficult, unless we are talking about a massive web application with hundreds of stored procedures.

|||

I've loaded the sql server 2005 express, I do have the sql 2005 server but I have to figure out how to run install with a script as I have 2000 on my machine.....

I can not figure out how to run a maintenance using this express version to save my life....Is anyone willing to give me a hand? I sure would apprieciate it.