noobie question on CSV Flat Files

Hi there,

I am connecting to a CSV file. When I look at the raw CSV, most of rows look something like this:

"19056","CD","Rick James"
These rows work fine but I run it to trouble when some rows look like this in the raw form:

"134530","Poster","Elizabeth on the set of "Giant", 1955"

You can see the issue that will arrise, SSIS parses this as 4 columns. Note: In the "Flat File Connection Manager" I have the "text qualifier" set to ".

Any suggestions as to how I might process files that have this type of situation? Maybe some sort of pre-process is necessary?

Other than that I've had great success with the other components and I am enjoying SSIS very much, great product!

Flat File Source does not support Embedded Qualifiers. Parsing columns that contain data with text qualifiers will fail at run time.You can use the Flat File Source to load the data as unqualified data and use a script component later to strip off the qualifiers downstream. You can also write a custom component to do the same. There is an Undouble component available for download from

http://www.microsoft.com/downloads/details.aspx?FamilyID=B51463E9-2907-4B82-A353-E15016486E1D&displaylang=en

which you can use.

|||

Thanks Ranjeeta,

This is kind of what I figured would be the case. I'll ask the publisher of the CSV to perhaps rethink their practice of embedded qualifiers. If I have no luck with that, I'll have to do something similar to what you're describing. Thanks for the link!

Non-release version (600) is not supported by this version of SQL Server

I downloaded the 101 Samples installation (i.e. 101SamplesCS.msi) from Microsoft's website, which contains SQL Server database files.

While working with the databases in the "Data Access" samples from the 101 Samples projects, I get the following error:

"Database <mdf_name> cannot be upgraded because its non-release version (600) is not supported by this version of SQL Server. You cannot open a database that is incompatible with this version of sqlservr.exe. You must re-create the database..."

I assume the database files were created with a beta or CTP version of SQL Server 2005. Does anyone know where I can get an updated version of these database files or scripts to update them?

Please help.

Mike.

I was getting this error back with the Beta versions when it was updated to Beta 2 and the last of the CTP. This generally means that the database file was created with an older version of the express products and can not go through the automatic upgrade processes. To fix it I had to get the SQL Scripts and re create the database structure.

If you have a look at the mdf name and post that we might be able to direct you to the latest versions, but you might find that if you download the latest samples from the downloads site for the SQL Express product you might get the file you need. More then likley it will be the northwind, pups or adventure works database.

|||

the error is caused by having a database that is an older format, usually beta. I believe the 101 Code Samples have been updated recently to contain release format databases. You can find the download link at http://msdn.microsoft.com/vstudio/downloads/101samples/default.aspx.

Try installing a fresh copy of the samples and see if they work. I can confirm the 'Multiple Active ResultSets' sample is able to load the database without a problem.

Mike

|||

I am having an identical problem with the plants database - used in the XPath/XSLT data sample - I've tried reloading the plants.mdf from both the latest c# & VB.net sample on the VS 2005 101 samples with no luck. The actual error is

Database '9D5A6E69A8EF2325FC6D4339CED21FB2_CS101SAMPLESDATAACCESS\XPATH AND XSLT TRANSFORMATIONS ENHANCEMENTS\XPATHXSL\DATABASE\PLANTS.MDF' cannot be upgraded because its non-release version (600) is not supported by this version of SQL Server. You cannot open a database that is incompatible with this version of sqlservr.exe. You must re-create the database.

|||

I would post this issue to the Feedback Center (http://connect.microsoft.com) for Visual Studio, since this is there sample. VS will need to update the sample as opening the file would require a pre-release build of SQL Server 2005 that is not available.

Regards,

Mike

|||

I note I can work around this by using the equivalent PlantInfo table in the C:\Documents and Settings\dlaub\My Documents\MSDN\CS101SamplesAll\CS101SamplesDataAccess\Using the XML data type with SQL Server 2005\XMLDataType\Database\XMLData.mdf database

You have to tweak the source code a bit (different database name, table name, column names)

And you just create a new table in ANY sql 2005 database - all this table has is an identity column and a xml column

|||

This problem

"cannot be upgraded because its non-release version (600) is not
supported by this version of SQL Server. You cannot open a database that
is incompatible with this version of sqlservr.exe. You must re-create
the database."

still exists in the testdata.mdf database (dated 2006-02-20) shipped with the 'DataReader vs. DataSet comparision' example in the CS101SamplesDataAccess folder of the CS101SamplesAll which I have downloaded several times most recently in April 2007.

I'm running Visual Studio 2005 Standard Edition SP1

Robert Wishlaw

Non-release version (600) is not supported by this version of SQL Server

I downloaded the 101 Samples installation (i.e. 101SamplesCS.msi) from Microsoft's website, which contains SQL Server database files.

While working with the databases in the "Data Access" samples from the 101 Samples projects, I get the following error:

"Database <mdf_name> cannot be upgraded because its non-release version (600) is not supported by this version of SQL Server. You cannot open a database that is incompatible with this version of sqlservr.exe. You must re-create the database..."

I assume the database files were created with a beta or CTP version of SQL Server 2005. Does anyone know where I can get an updated version of these database files or scripts to update them?

Please help.

Mike.

I was getting this error back with the Beta versions when it was updated to Beta 2 and the last of the CTP. This generally means that the database file was created with an older version of the express products and can not go through the automatic upgrade processes. To fix it I had to get the SQL Scripts and re create the database structure.

If you have a look at the mdf name and post that we might be able to direct you to the latest versions, but you might find that if you download the latest samples from the downloads site for the SQL Express product you might get the file you need. More then likley it will be the northwind, pups or adventure works database.

|||

the error is caused by having a database that is an older format, usually beta. I believe the 101 Code Samples have been updated recently to contain release format databases. You can find the download link at http://msdn.microsoft.com/vstudio/downloads/101samples/default.aspx.

Try installing a fresh copy of the samples and see if they work. I can confirm the 'Multiple Active ResultSets' sample is able to load the database without a problem.

Mike

|||

I am having an identical problem with the plants database - used in the XPath/XSLT data sample - I've tried reloading the plants.mdf from both the latest c# & VB.net sample on the VS 2005 101 samples with no luck. The actual error is

Database '9D5A6E69A8EF2325FC6D4339CED21FB2_CS101SAMPLESDATAACCESS\XPATH AND XSLT TRANSFORMATIONS ENHANCEMENTS\XPATHXSL\DATABASE\PLANTS.MDF' cannot be upgraded because its non-release version (600) is not supported by this version of SQL Server. You cannot open a database that is incompatible with this version of sqlservr.exe. You must re-create the database.

|||

I would post this issue to the Feedback Center (http://connect.microsoft.com) for Visual Studio, since this is there sample. VS will need to update the sample as opening the file would require a pre-release build of SQL Server 2005 that is not available.

Regards,

Mike

|||

I note I can work around this by using the equivalent PlantInfo table in the C:\Documents and Settings\dlaub\My Documents\MSDN\CS101SamplesAll\CS101SamplesDataAccess\Using the XML data type with SQL Server 2005\XMLDataType\Database\XMLData.mdf database

You have to tweak the source code a bit (different database name, table name, column names)

And you just create a new table in ANY sql 2005 database - all this table has is an identity column and a xml column

|||

This problem

"cannot be upgraded because its non-release version (600) is not
supported by this version of SQL Server. You cannot open a database that
is incompatible with this version of sqlservr.exe. You must re-create
the database."

still exists in the testdata.mdf database (dated 2006-02-20) shipped with the 'DataReader vs. DataSet comparision' example in the CS101SamplesDataAccess folder of the CS101SamplesAll which I have downloaded several times most recently in April 2007.

I'm running Visual Studio 2005 Standard Edition SP1

Robert Wishlaw

Non-release version (600) is not supported by this version of SQL Server

I downloaded the 101 Samples installation (i.e. 101SamplesCS.msi) from Microsoft's website, which contains SQL Server database files.

While working with the databases in the "Data Access" samples from the 101 Samples projects, I get the following error:

"Database <mdf_name> cannot be upgraded because its non-release version (600) is not supported by this version of SQL Server. You cannot open a database that is incompatible with this version of sqlservr.exe. You must re-create the database..."

I assume the database files were created with a beta or CTP version of SQL Server 2005. Does anyone know where I can get an updated version of these database files or scripts to update them?

Please help.

Mike.

I was getting this error back with the Beta versions when it was updated to Beta 2 and the last of the CTP. This generally means that the database file was created with an older version of the express products and can not go through the automatic upgrade processes. To fix it I had to get the SQL Scripts and re create the database structure.

If you have a look at the mdf name and post that we might be able to direct you to the latest versions, but you might find that if you download the latest samples from the downloads site for the SQL Express product you might get the file you need. More then likley it will be the northwind, pups or adventure works database.

|||

the error is caused by having a database that is an older format, usually beta. I believe the 101 Code Samples have been updated recently to contain release format databases. You can find the download link at http://msdn.microsoft.com/vstudio/downloads/101samples/default.aspx.

Try installing a fresh copy of the samples and see if they work. I can confirm the 'Multiple Active ResultSets' sample is able to load the database without a problem.

Mike

|||

I am having an identical problem with the plants database - used in the XPath/XSLT data sample - I've tried reloading the plants.mdf from both the latest c# & VB.net sample on the VS 2005 101 samples with no luck. The actual error is

Database '9D5A6E69A8EF2325FC6D4339CED21FB2_CS101SAMPLESDATAACCESS\XPATH AND XSLT TRANSFORMATIONS ENHANCEMENTS\XPATHXSL\DATABASE\PLANTS.MDF' cannot be upgraded because its non-release version (600) is not supported by this version of SQL Server. You cannot open a database that is incompatible with this version of sqlservr.exe. You must re-create the database.

|||

I would post this issue to the Feedback Center (http://connect.microsoft.com) for Visual Studio, since this is there sample. VS will need to update the sample as opening the file would require a pre-release build of SQL Server 2005 that is not available.

Regards,

Mike

|||

I note I can work around this by using the equivalent PlantInfo table in the C:\Documents and Settings\dlaub\My Documents\MSDN\CS101SamplesAll\CS101SamplesDataAccess\Using the XML data type with SQL Server 2005\XMLDataType\Database\XMLData.mdf database

You have to tweak the source code a bit (different database name, table name, column names)

And you just create a new table in ANY sql 2005 database - all this table has is an identity column and a xml column

|||

This problem

"cannot be upgraded because its non-release version (600) is not
supported by this version of SQL Server. You cannot open a database that
is incompatible with this version of sqlservr.exe. You must re-create
the database."

still exists in the testdata.mdf database (dated 2006-02-20) shipped with the 'DataReader vs. DataSet comparision' example in the CS101SamplesDataAccess folder of the CS101SamplesAll which I have downloaded several times most recently in April 2007.

I'm running Visual Studio 2005 Standard Edition SP1

Robert Wishlaw

Non-clustered indexes on 1 separate fileGroup?

Hi Guys,

I am reviewing the storage structure of my growing db.

I am going to create multiple FileGroups and db files.
Most of the filegroups will be used to allow table partitioning and put the heavily used partitions on different storage than the read-only archives. TempDB will also have its own filegroup/storage.

For Indexes, I have a doubt. I am sure I can have all my non-clustered indexes on a separate fileGroup and storage but what about primary keys and/or clustered indexes?

Should I move them to the same filegroup than the non-clustered indexes or should I leave them with the data? What would be best?

I am running a 100GB reporting datamart on SQL2005 enterprise, There are almost no transactions, just a daily and weekly refresh. I will soon have more storage, SAN or NetApp, not sure yet.

Thanks,

Philippe

Hi

Moving your indexes to a seperate filegroup can improve the parallism of some querries that need to work with indexes and then do a bookmark lookup afterwards. If you have a VLDB like you said you should consider doing it, since the indexes cant be kept in memory all the time. So when you access the indexes it will not block the retrieval of your data from the other partition.