>> Object_ID not indicative of order of creation

There seems to be nothing else to indicate the order of creation.

Something like my query will produce the results in the order...

@t is a TEST table.

1. Take the query:

-- The Query

SELECT TID

 ,COUNT(DISTINCT TYPE) AS LOGON_TYPE_RECORD

 ,COUNT(CASE WHEN TYPE = 'JPJ' THEN 1 END) AS JPJ_RECORD

 ,COUNT(CASE WHEN TYPE = 'JPN' THEN 1 END)...

Assuming objectID indicates order of creation:

SELECT O.objectID

 ,O.objectName

FROM tblObject O

 LEFT JOIN (

  SELECT DISTINCT R.dependent_objectID

  FROM tblDependency R ) D

 ON O.objectID = D.dependent_objectID

ORDER BY

 CASE WHEN D.dependent_objectID IS NULL

 THEN 0

 ELSE 1 END

 ,O.objectID

In this type of query you need to ALIAS all tables and use the ALIAS with the columns. Also, in this instance, I can see no point in using a...

Interesting...

With SQL2000:

In Example A the batch actually fails to compile so the transaction does not even begin. This is what I would expect to happen.

In Example B the batch does...

Without knowing the details, it looks as though it will work.

I would be inclined just to have an UPDATE statement rather than call the DELETE and INSERT SPs.

If you want...

Similar to this thread:

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=145&messageid=315718

You will need to use CASE to make zero return NULL.

ps You may do better if the data is normalized.

Do you mean SELECT?

INSERT YourTable

SELECT Col1, Col2, ...

FROM YourView

There is probably a better way:

-- Test data

DECLARE @t TABLE

(

 Seq INT not null

 ,RowID INT not null

 ,DataSample VARCHAR(20) COLLATE DATABASE_DEFAULT NOT NULL

)

INSERT @t

SELECT 1, 1, '111111' UNION ALL

SELECT 2, 2, 'A'...

Thanks for the feedback.

If you REALLY have to:

SET QUOTED_IDENTIFIER ON

GO

SET ANSI_NULLS ON

GO

CREATE PROCEDURE dbo.MyProc

( @EmployeeName VARCHAR(50)

 -- MONEY may be better for Sal, or at least DECIMAL(18,4)

 ,@Sal NUMERIC(18,2)

 ,@EmpID INT OUTPUT )

AS

SET NOCOUNT ON

--SET...

As you are not raising any special errors, why not keep it simple:

SET QUOTED_IDENTIFIER ON

GO

SET ANSI_NULLS ON

GO

CREATE PROCEDURE dbo.MyProc

( @EmployeeName VARCHAR(50)

 -- MONEY may be better for Sal, or at...

Something like the following should be more efficient as the table will only be scanned once:

-- Test Data

DECLARE @t TABLE

(

 TID INT NOT NULL PRIMARY KEY

 ,TDate1 DATETIME NULL

 ,TDate2 DATETIME NULL

 ,TDate3 DATETIME...

In SQL2000, I do not think defaults are allowed to refer to other columns in the table.

You may be able to get away with this in SQL2005.

-- Test Data

DECLARE @t TABLE

(

 TID CHAR(5) COLLATE DATABASE_DEFAULT NOT NULL

 ,TYPE CHAR(3) COLLATE DATABASE_DEFAULT NOT NULL

)

INSERT @t

SELECT 'KL202', 'JPJ' UNION ALL

SELECT 'KL202', 'JPJ' UNION ALL

SELECT 'KL202', 'JPN' UNION ALL

SELECT 'KL202', 'JIM'...