ERROR: Create DMO Object.
Source: ODSOLE Extended Procedure
Description: Invalid class string

Using SQL Server 2008R2

In addition, has anyone amended the scripts to take account of different TABLE_SCHEMA values in the SELECT statements?

Thanks,
Maria Pia Fernandez

Error : Load Object, dump buffer
I am on SqlServer2005

Can someone help me?

This information is very helpful. If you would be able to fix the link to the downloadable code and documentation, it would be very much appreciated.

Thanks and have a great day,
Dave

Thanks,
Nick

ERROR: Connect.
Source: ODSOLE Extended Procedure
Description: [Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied.
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen (Connect()).

Any idea how to fix this? I am sysadmin on the server.

Another issue I has with these scripts was that FOREIGN KEY CONSTRAINTS generated duplicate entries on script 1 and 3, to solve this I added a Distinct to the relevent select statements.

Other than that these scripts worked great, Cheers for publishing them.

The database I need to convert used alot of user defined types, to support this I changed the select in script 2 as follows. Basically it checks the DOMAIN_NAME which on my system contained the name of the user defined type for the column. (User defined types appear to take the default collation of the database so this is not specified)
——-

SELECT [SET_COLLATION] = (‘ALTER TABLE [' + TABLE_NAME + '] ALTER COLUMN [' + COLUMN_NAME + '] ‘ +
CASE WHEN DOMAIN_NAME is null THEN
DATA_TYPE +
CASE WHEN
DATA_TYPE IN (‘text’,'ntext’) THEN
‘ COLLATE ‘ + @collation
ELSE
‘(‘+CAST(CHARACTER_MAXIMUM_LENGTH AS VARCHAR(10))+’)’ + ‘ COLLATE ‘ + @collation
END
ELSE
DOMAIN_NAME
END
+ CASE IS_NULLABLE WHEN ‘NO’ THEN ‘ NOT NULL’ WHEN ‘YES’ THEN ‘ NULL’ END

)
COLLATE Latin1_General_CI_AS
FROM INFORMATION_SCHEMA.columns
WHERE
TABLE_NAME N’dtproperties’ AND
OBJECTPROPERTY(OBJECT_ID(TABLE_NAME), N’IsUserTable’) = 1 AND
COLLATION_NAME @collation

Script: Pre-Script_0_DBADB.sp_scriptObject.sql
Line 81
Should be changed from:
EXEC @rc = sp_OAMethod @o_server , ‘Connect’, NULL, ‘(local)’

to

EXEC @rc = sp_OAMethod @o_server , ‘Connect’, NULL, @@SERVERNAME

The above corrects the “connect” issue when running the scripts against a named instance.

These scripts were technically designed to run on a SQL 2000 instance, where the generated DDL could then be run on any version. So, technically this isn’t an error. However, I’ve found that these scripts do run fine on SQL’05 and SQL’08. However, Microsoft dropped DMO in 2005 and replaced it with SMO. So, in order for these to run, you may need to install DMO with the Backward Compatability package which can be downloaded at:

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en

@CJ – Thanks for spotting that. Sounds like you’re current collation is Case Sensitive. So, by correcting the case for .COLUMNS, it makes the script much more generic – exactly what I was trying to achieve.

@Kevin – Apologies for not posting this sooner. Your connection issue is addressed in my first bullet point above.

This was a very helpfull article and scripts.

There are 2 errors
1: in de Usage.txt it says you need to create the database named ‘DBA_Data’ wich should be DBADB (as mentioned in the article)
2: when you use these scripts in 2005, you have to change
Pre-Script_2_CHANGE_COLLATIONS:
change
FROM INFORMATION_SCHEMA.columns
into
FROM INFORMATION_SCHEMA.COLUMNS

After this it works like a charm.

ERROR: Connect for each call.

I am sysadm, and do not know what is wrong. I need to have something by friday, and am researching another method that does about the same thing, but is more manual, and is taking much longer. any suggestions as to what I am doing wrong would be appreciated.

One remark, I had to run sp_configure to enable ‘Ole Automation Procedures’ during generation of the CREATE script.