oops .. overlooked that because we don't use it in that way

- with SQLServer2005 you can perform this by granting at schema level.

- In sqlserver2000 you can only add the user to the db_owner group of the database. But then that...

just my 2ct

nvarchar(..) is double byte so nvarchar(1000) takes max 2000 bytes + length indicator.

making it ntext will allow you to store up to 2G for that column.

Downsides are :

globSMOSrv = the smo.server

as stated in the first of this thread :

oDatabase = globSMOSrv.Databases.Item("master")

in VS2005 immediate window

?oDatabase.CompatibilityLevel

Version80 {80}

?globSMOSrv.Information.VersionString

"9.00.1399.06"

Now what's the point of not having at least the system...

The strange thing is that I can implement storedprocs that use e.g. CTE's and execute them without a problem or warning

if this is not a sql2000 sp4 system ...

There have been issues with parallelism with sp3(a), and it took a while until there was a hotfix to overcome the buggy...

You 'll need your db in bulk or full recovery mode.

check out http://www.sqlservercentral.com/columnists/kKellenberger/restoringtoapointintime.asp

From SQLServer 2005 BOL :

Because SMO is compatible with SQL Server version 7.0, SQL Server 2000, and SQL Server 2005, you easily manage a multi-version environment.