Hi Bruce

This works correct, but why access the table twice? My first post should also work without accessing UserStats twice:

SELECT @UserId = 2

INSERT INTO dbo.UserStats

SELECT @UserId

...

Sure, the variable has only one value, but your SELECT might return many:

DECLARE @UserStats TABLE (UserId INT)

INSERT INTO @UserStats

...

Hi

I just tried on SQL Server 2008 and this seems to work:

CREATE TABLE TestDefault (Id INT)

GO

INSERT INTO TestDefault SELECT 1

GO

ALTER TABLE TestDefault ADD Dt DATETIME NOT NULL DEFAULT GETDATE()

GO

SELECT *...

Lynn, please correct me if I'm wrong but the original code would only once insert the @UserId if does not yet exist. Your code seems to create a new row...

Nothing to hide. Just updated my profile picture 😉

Great feature, [] works even for multi-line:

CREATE TABLE [

] ([.] INT, [

] INT, [ ]]

] INT,"""" INT)

INSERT INTO [

] SELECT 1, 2, 3, 4

SELECT []]].[

], [,].[ ]]

] [[], [,].["],[[[

].[

],[,].[.]

FROM [

]...

Hi

Because you said that neither linked server nor openrowset is an option I think there is no other way than a server-client-server transfer.

* Create a temp table (or a stateful...

:sick:

CREATE SCHEMA [%]

GO

CREATE TABLE [%].[%] (Id INT IDENTITY PRIMARY KEY, i INT, [-] INT, [AND] INT, [*] INT, [%] VARCHAR(10))

CREATE INDEX [master.sys.objects] ON [%].[%] ([-]) INCLUDE ([*])

INSERT INTO [%].[%] SELECT...

So, if your application currently works, why not just a "BEGIN TRANSACTION" at start and a "COMMIT TRANSACTION" after all was done?

Another approach, to avoid a long time lock might...

😀

Just one thing missing:

DECLARE @t TABLE (Id INT, [*] VARCHAR(10))

INSERT INTO @t SELECT 1, 'abc'

SELECT [*] FROM @t

Hope The Thread forgives this kind of source code!

Just to ensure, if you say "Linked server" is not an option. Does this include "OPENROWSET"?

Sorry, forgot: How often did you have a column "Group" or even "From" (and "To") 😀

I noticed the sarcasm and I noticed the 'NULL'. I've just been bothered by the thread. If the question would be this don't work:

SELECT blah FROM anywhere

UNION ALL

SELECT 'NULL'

.. I...

Hi

What about just a simple INSERT SELECT WHERE:

DECLARE @users TABLE (Id INT)

DECLARE @UserId INT

-- New user

SELECT @UserId = 1

INSERT INTO @users

SELECT @UserId

WHERE NOT EXISTS...

Alvin,

I have to confirm Bob. Because I am more a C#y than a VBly I would say "null" is always better than "Nothing"

BTW: In contrast to Bob I really hope...