Comments on: Two ways to find / drop a default constraint without knowing its name https://lobsterpot.com.au/blog/2007/11/26/two-ways-to-find-drop-a-default-constraint-without-knowing-its-name/ Wed, 28 Nov 2007 01:42:22 +0000 hourly 1 https://wordpress.org/?v=7.1.2 By: Rob Farley https://lobsterpot.com.au/blog/2007/11/26/two-ways-to-find-drop-a-default-constraint-without-knowing-its-name/#comment-510 Wed, 28 Nov 2007 01:42:22 +0000 /blogs/robfarley/archive/2007/11/26/two-ways-to-find-drop-a-default-constraint-without-knowing-its-name.aspx#comment-510 Ah, nice tip. Thanks Darren.

]]> By: Darren Gosbell https://lobsterpot.com.au/blog/2007/11/26/two-ways-to-find-drop-a-default-constraint-without-knowing-its-name/#comment-509 Tue, 27 Nov 2007 04:00:00 +0000 /blogs/robfarley/archive/2007/11/26/two-ways-to-find-drop-a-default-constraint-without-knowing-its-name.aspx#comment-509 The schema is the issue with the powershell script. I thought I would have been able to pipe the Tables collection to get-member to see it’s methods, but PowerShell was too smart and pulled out the first table so I ended up using reflector to find out that the TableCollection class has an Item() method which has an overload that takes 2 strings, the name and the schema.

So the following should work.

[reflection.assembly]::LoadwithPartialName(“Microsoft.SQLServer.SMO”)
$sql = New-Object ‘Microsoft.sqlserver.management.smo.server’ ‘localhost’
$sql.Databases[“AdventureWorks”].Tables.Item(“Department”,”HumanResources”).Columns[“ModifiedDate”].DefaultConstraint.Drop()

]]>