Have they provided you an instance name? e.g. 203.84.233.54\SQL2005

I was just able to generate your error trying to connect a local instance by using (local) instead of (local)\instanceName

Here's...

Hi Mark Finnie,

This is correlated subquery is guaranteed to NOT be the most efficient way to do this. However, it will get you there till the next respondent proposes...

Is SQL Server also running under the local system account?

If not, does the local system account have permission to access SQL Server?

This will keep you from having to duplicate your column names / complex formulae on both sides of the = operator. 

If @param1 is null, query planner just pulls everything...

since sp_addtype just uses the default collation for the UDT's base datatype, after calling the procedure to create your type, you could manually change the collation for the UDT in the...

You can set the column level collation to case sensitive on the appropriate columns without affecting table and column names, i.e.,

alter table <table_name>

   alter column <column_name> [varchar] (50) COLLATE Latin1_General_CS_AS NOT NULL

You...

the scptxfr tool comes with sql server and generates the objects in a runnable order...

C:\>scptxfr /s <serverName>\<instance> /I /d <databaseName> /f <scriptOutputFile.sql>