Viewing 15 posts - 811 through 825 (of 827 total)
sysdepends lists tables only if they are in the same database and the sp is created after the table. To update syspedends please ALTER PROCEDURE and then run exec sp_MSdependencies...
January 2, 2009 at 2:54 am
I hate UNICODE. It uses a lot memory uselessly. It brings applications to BAD performance. :angry:
January 2, 2009 at 1:30 am
Please, try this one:
exec sp_MSdependencies N'[dbo].[mysp_elab]', null, 1053183
Third parameter is 1053183, that means only table named in the sp.
Without parms, it returns all dipendencies: table used in the sp and...
January 2, 2009 at 1:23 am
If you do not use dynamic sql in your sp, you have the sysdepends table with all dependencies between objects.
Here you are:
SELECT object_name(id) as sp,object_name(depid) as dep_obj FROM sysdepends
WHERE...
December 30, 2008 at 12:47 am
From now, every time you'll write a joined query, you'll think to Elthon JOIN.
In confidence, I prefer Freddy Mercury e his band The QUEEN.
December 29, 2008 at 10:02 am
GilaMonster (10/14/2008)
Hence there's an implicit Order by 1 ASC on the statement.
Also the DISTINCT clause and the GROUP BY perform an implicit ORDER BY for all cols, but "IMPLICIT" is...
October 14, 2008 at 2:26 am
Without the ORDER BY clause, you can not predict the order of rows.
NULL, 1 and 1, NULL are both possible.
In the future release of sqlserver or in another DBMS, the...
October 14, 2008 at 12:59 am
brewmanz (10/13/2008)
T
It always is correct WITH THIS SET OF DATA. Try adding a couple of zero(e)s at the end of each of the 3 numbers and watch "Msg 8115, Level...
October 14, 2008 at 12:38 am
Main rule is never to use float, because of unwanted effetcs:
Here the version with decimal. It always is correct.
DECLARE @suma float, @SumB float
DECLARE @MyFloat1 float, @MyFloat2 float, @MyFloat3 float
DECLARE @MyTable...
October 13, 2008 at 10:17 am
That's true:
DECLARE @suma float, @SumB float
DECLARE @MyFloat1 float, @MyFloat2 float, @MyFloat3 float
DECLARE @MyTable table
(
ID int primary key identity,
NumA float,
NumB float
)
SET @MyFloat1 = 10000000000020000
SET @MyFloat2 = -10000000000010000
SET @MyFloat3 = 1
INSERT INTO...
October 13, 2008 at 7:17 am
Good idea! But just for few rows result set. Else it takes too long to run if put the result set in join with another table.
August 6, 2008 at 7:12 am
Another thing never said: when creating temp table is better adding the "collate" to char/varchar/text etc. cause of different collate in tempdb e the current db.:w00t:
July 17, 2008 at 1:03 am
Viewing 15 posts - 811 through 825 (of 827 total)