Ditto!

LOL.. He also wants "random" and "unique"... Given that any randomly generated number always has the potential to collide with another randomly generated number, the base requirements are a contradiction...

• This reply was modified 1 year, 6 months ago by  Jason A. Long.

This is a big topic... To big for a simple forum reply. So rather that dive into details, I would suggest you start with an "adjacency list" model. For example,...

It shouldn't be too bad...

Thanks Jeff... I've haven't actually gone anywhere. I just do more reading than posting these days (mostly due to reading on an iOS devise).

Every once in awhile,...

• This reply was modified 1 year, 6 months ago by  Jason A. Long.

I read it as "the number should be between 10 and 15 digits in length and the first two digits must be 11".

Some clarification from the OP would be helpful.

Something like this...

WITH 
cte_n1 (n) AS (SELECT 1 FROM (VALUES (1),(1),(1),(1),(1),(1),(1),(1),(1),(1)) n (n)),-- 10
cte_n2 (n) AS (SELECT 1 FROM cte_n1 a CROSS JOIN cte_n1 b),-- 100
cte_n3 (n)...

reduce the length to

The numbers should begin with 11. The minimum length of the number should be 10 The maximum length of the number should be 15 Need...

• This reply was modified 1 year, 6 months ago by  Jason A. Long.

Generally speaking… Yes, you can create functions in the master database and referent them from any other database using the 3 part, fully qualified name.

That said, if the function definition...

You are 100% correct Jeff. Complete brain fart on my part. Please disregard my previous comment.

You could create a separate stored procedure that accepts a spid as an input parameter.

The stored proc would be a simple WAITFOR command that waits for a period of time...

The question is still technically "ambiguous" given that the following also works...

CREATE TABLE #TestData (
int_val int NOT NULL 
);

INSERT #TestData (int_val)
SELECT 
tvc.int_val
FROM
( VALUES 
(1),(2),(3),(4),(5),(6),(7),(8),(9),(10),(11),(12),
...
(1189),(1190),(1191),(1192),(1193),(1194),(1195),(1196),(1197),(1198),(1199),(1200)
) tvc (int_val);

Oh, I get that.  Just every once in a while, you want to put something together for a "one-off what-if" and thing like this come in handy.

Agreed.

Just keep in mid that, "just because you can, doesn't mean you should"... Super long value lists can really eat up compile memory and compile time.

If you want to additional...

• This reply was modified 1 year, 10 months ago by  Jason A. Long.

And just for the fun of it, I just did a successful test with 120,000 values.