Recent changes to bugshttps://sourceforge.net/p/script-sql-db/bugs/2008-03-14T20:41:11ZRecent changes to bugsSqlServer.Management.Smo.UnsupportedFeatureExceptiion2008-03-14T20:41:11Z2008-03-14T20:41:11ZAnonymoushttps://sourceforge.net/u/userid-None/https://sourceforge.net33712c7ed3592c026370875c4c59c4c33e87bb2a<div class="markdown_content"><p>While scripting database on MS SQL 2005 Express server, call to db.FullTextCatalogs throws exception of type Microsoft.SqlServer.Management.Smo.UnsupportedFeatureException</p></div>ScriptAllDBs Error2007-09-28T21:44:48Z2007-09-28T21:44:48ZAnonymoushttps://sourceforge.net/u/userid-None/https://sourceforge.neta7f74e049c6ce0de2101a6e45c1f62d2291193eb<div class="markdown_content"><p>ScriptAllDBs.exe tries to call the ScriptDB executable but it doesn't seem to pass over the parameters that ScriptDB is expecting. Specifically it doesn't pass over the connection string information. This causes ScriptDB to fail.</p>
<p>Is there a newer version? </p></div>System tables not filtered properly2007-03-06T21:07:22Z2007-03-06T21:07:22ZAnonymoushttps://sourceforge.net/u/userid-None/https://sourceforge.netb89f6f81790b6903496699d7e7ecac6f91deceb1<div class="markdown_content"><p>The system status of a table is determined by owner (dbo) and table prefix (sys). This prevents user tables beginning with sys that are owned by dbo from being scripted.</p>
<p>scriptdb.cs line 273:<br />
// skip system tables<br />
//if (tbl.Schema == "dbo" && tbl.Name.StartsWith("sys"))<br />
...</p>
<p>Recommend using the IsSystemObject of Table to determine the system status of tables:<br />
if (tbl.IsSystemObject)<br />
...</p>
<p><a href="http://msdn2.microsoft.com/en-us/library/microsoft.sqlserver.management.smo.table.issystemobject.aspx" rel="nofollow">http://msdn2.microsoft.com/en-us/library/microsoft.sqlserver.management.smo.table.issystemobject.aspx</a></p>
<p>This could also apply to views, functions, procedures and users</p></div>