|
|
-
Great stuff guys!<br>
Here is my two cents :-)
List all procedures and the tables they reference:
CREATE FUNCTION dbo.FullSPNames()
RETURNS @SPNames TABLE (FullSPName nvarchar(40))
AS BEGIN
INSERT INTO @SPNames(FullSPName)
SELECT...
|
-
Dimitrios Staikos Commented 9 Months ago through Just Learned
Interesting!
Btw, when items are created WITH ENCRYPTION the definition is NULL....
|
-
Dimitrios Staikos Commented 9 Months ago through Just Learned
Interesting!
Btw, when items are created WITH ENCRYPTION the definition is NULL....
|
-
Well, you are right of course, it never occurred to me to use DISTINCT along with * cause I practically never use * in the first place. :-D...
|
-
OK, that's cool, if you want to compare more than 3-4 rows it makes sense.
It is quite unusual I think that two tables have the exactly same rows as in your example.
However if someone brings in some data for import and you want to clear out the dupli...
|
-
Is there something I can do with INTERSECT/EXCEPT that I cannot do with JOIN or IN?
Coz this looks like syntactic sugar to me....
|
-
Interview questions and answers on various SQL Server areas such as Database Administration, TSQL Development, BI etc....
|
-
I ended my last tip about triggers on the note 'Triggers should always be written to handle multiple rows'. I searched online for different methods people have been using on handling trigger based solutions and thought it would make a good learning t...
|
-
I ended my last tip about triggers on the note 'Triggers should always be written to handle multiple rows'. I searched online for different methods people have been using on handling trigger based solutions and thought it would make a good learning t...
|
-
Dimitrios Staikos Commented 1 Years ago through Puzzles
Well, I didn't have much time to work on improving or testing performance, for example even little things like the comma when concatenating the date strings is totally unnecessary, only helped in readability while testing the query. Then I could probably f
|