We know how difficult it can be to evaluate Wi-Fi vendors, so we created this helpful Wi-Fi Buyer's Guide to help you find the Wi-Fi vendor that's right for your business! Download the guide and get started on our checklist today!
Solved
Powershell / SMO -- scripting out SQL database ddl -- non dbo schema problem
Posted on 2012-12-28
Trying to traverse all objects in the SQL Server database, scripting the object creation to .sql file, to be stored within a source code repository.
We are using Powershell calling SMO to create the DDL files. Basically, it works well for all dbo schema objects. Any other user defined schemas are not being processed correctly.
The Powershell script is attached. At line 21 you can see where we tried to handle the schema with this: $Object=$Schema + "." + $Object
EXAMPLES:
This works:
./schemaextract.ps1 "c:\temp" "ServerName" "DatabaseName" "Table" "dbo" "TableA"
This works, but the object is qualified with ‘dbo’, instead of ‘OtherSchema’. ‘TableA’ exists within both schemas:
./schemaextract.ps1 "c:\temp" "ServerName" "DatabaseName" "Table" "OtherSchema" "TableA"
This fails, presumably because ‘TableB’ is only in ‘OtherSchema’:
./schemaextract.ps1 "c:\temp" "ServerName" "DatabaseName" "Table" "OtherSchema" "TableB"
We have tried unsuccessfully to pass in the schema name. When attempting to do so, this is the failure:
PS C:\mssql\tools> ./schemaextract.ps1 "c:\temp" "ServerName" "DatabaseName" "Table" "dbo" "TableA"
Directory: C:\temp\DatabaseName
Mode LastWriteTime Length Name
---- ------------- ------ ----
d---- 12/21/2012 2:46 PM Tables
Multiple ambiguous overloads found for "Script" and the argument count: "1".
At C:\mssql\tools\SchemaExtra
+ $scrp.Script <<<< ($db.Tables["$Object"])
+ CategoryInfo : NotSpecified: (:) [], MethodException
+ FullyQualifiedErrorId : MethodCountCouldNotFindBes
We did this several years back with SMO -- no problems at all. But, we had only the 'dbo' schema at that time. Is anyone able to advise?
SchemaExtract.txt
We are using Powershell calling SMO to create the DDL files. Basically, it works well for all dbo schema objects. Any other user defined schemas are not being processed correctly.
The Powershell script is attached. At line 21 you can see where we tried to handle the schema with this: $Object=$Schema + "." + $Object
EXAMPLES:
This works:
./schemaextract.ps1 "c:\temp" "ServerName" "DatabaseName" "Table" "dbo" "TableA"
This works, but the object is qualified with ‘dbo’, instead of ‘OtherSchema’. ‘TableA’ exists within both schemas:
./schemaextract.ps1 "c:\temp" "ServerName" "DatabaseName" "Table" "OtherSchema" "TableA"
This fails, presumably because ‘TableB’ is only in ‘OtherSchema’:
./schemaextract.ps1 "c:\temp" "ServerName" "DatabaseName" "Table" "OtherSchema" "TableB"
We have tried unsuccessfully to pass in the schema name. When attempting to do so, this is the failure:
PS C:\mssql\tools> ./schemaextract.ps1 "c:\temp" "ServerName" "DatabaseName" "Table" "dbo" "TableA"
Directory: C:\temp\DatabaseName
Mode LastWriteTime Length Name
---- ------------- ------ ----
d---- 12/21/2012 2:46 PM Tables
Multiple ambiguous overloads found for "Script" and the argument count: "1".
At C:\mssql\tools\SchemaExtra
+ $scrp.Script <<<< ($db.Tables["$Object"])
+ CategoryInfo : NotSpecified: (:) [], MethodException
+ FullyQualifiedErrorId : MethodCountCouldNotFindBes
We did this several years back with SMO -- no problems at all. But, we had only the 'dbo' schema at that time. Is anyone able to advise?
SchemaExtract.txt
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
7
2
9 Comments
what if you do replace this line:
$scrp.Script($db.Tables["$
by this line
$scrp.Script($db.Tables["$
$scrp.Script($db.Tables["$
by this line
$scrp.Script($db.Tables["$
Active 1 day ago
this is the error we get, angeliii:
PS C:\mssql\tools> ./schemaextract.ps1 "c:\temp" "SERVERNAME" "CTS" "Table" "
OtherSchema" "TableB"
Multiple ambiguous overloads found for "Script" and the argument count: "1".
At C:\mssql\tools\SchemaExtra
+ $scrp.Script <<<< ($db.Tables["$Schema.$Obje
+ CategoryInfo : NotSpecified: (:) [], MethodException
+ FullyQualifiedErrorId : MethodCountCouldNotFindBes
in this case, Table2 is there only in OtherSchema, not dbo.
If the table exists under 2 schemas, dbo and otherwise, the script works without error, but is only finding the dbo object.
If the object only exist in a schema other than dbo, the script errors out.
PS C:\mssql\tools> ./schemaextract.ps1 "c:\temp" "SERVERNAME" "CTS" "Table" "
OtherSchema" "TableB"
Multiple ambiguous overloads found for "Script" and the argument count: "1".
At C:\mssql\tools\SchemaExtra
+ $scrp.Script <<<< ($db.Tables["$Schema.$Obje
+ CategoryInfo : NotSpecified: (:) [], MethodException
+ FullyQualifiedErrorId : MethodCountCouldNotFindBes
in this case, Table2 is there only in OtherSchema, not dbo.
If the table exists under 2 schemas, dbo and otherwise, the script works without error, but is only finding the dbo object.
If the object only exist in a schema other than dbo, the script errors out.
this is what worked for me:
you can use the "where" code easily to limit the objects array to be scripted to what you need ... this may help to simplify the work.
apart from that, the only thing that made the code "fail" is when the output folder was "write protected" ...
hope this helps
[System.Reflection.Assembly]::LoadWithPartialName('Microsoft.SqlServer.SMO') | out-null
$s = new-object ('Microsoft.SqlServer.Management.Smo.Server') "$SQL_SERVER"
$db=$s.Databases["$Database"]
$tbls = $db.Tables | where { $_.Name -eq "Object" }
$tbl = $tbls | where { $_.Schema -eq "$Schema" }
$scrp = new-object ('Microsoft.SqlServer.Management.Smo.Scripter') ($s)
$scrp.Options.FileName = "c:\temp\test.sql"
$scrp.Options.ToFileOnly = $True
$scrp.Script($tbl)
you can use the "where" code easily to limit the objects array to be scripted to what you need ... this may help to simplify the work.
apart from that, the only thing that made the code "fail" is when the output folder was "write protected" ...
hope this helps
Featured Post
Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
A Stored Procedure in Microsoft SQL Server is a powerful feature that it can be used to execute the Data Manipulation Language (DML) or Data Definition Language (DDL).
Depending on business requirements, a single Stored Procedure can return differe…
Windocks is an independent port of Docker's open source to Windows. This article introduces the use of SQL Server in containers, with integrated support of SQL Server database cloning.
- SQL
- Microsoft SQL Server
- AWS
- Azure
- Docker
- *DevOps
Via a live example, show how to extract insert data into a SQL Server database table using the Import/Export option and Bulk Insert.
This videos aims to give the viewer a basic demonstration of how a user can query current session information by using the SYS_CONTEXT function
Suggested Courses
Course of the Month7 days, 4 hours left to enroll
704 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.