Viewing 15 posts - 46 through 60 (of 363 total)
You can almost put this into the "trick" category. It has other ramifications...
The Good:
You can use this syntax inside UDFs to not only get around the UDF
contraint...
Once you understand the BITs, all the pieces come together ![]()
March 3, 2004 at 2:31 pm
As noeld uses spt_values in Master, I do also for the same kind of usages. This table seems to perform even faster than any "user table" made with the same...
Once you understand the BITs, all the pieces come together ![]()
March 3, 2004 at 2:13 pm
A question about finding duplicates turns into a thread about not having duplicated (rehashed) posts ![]()
Anyway, I would...
Once you understand the BITs, all the pieces come together ![]()
March 3, 2004 at 2:00 pm
Not the fastest execution, but try ....
select * Into #Temp
from OpenRowset('SQLOLEDB',
'Server=(local);Trusted_Connection=yes',
'Set Nocount On Exec Master.dbo.sp_Who') A
Select * From #Temp
Once you understand the BITs, all the pieces come together ![]()
March 3, 2004 at 1:52 pm
How about just...
CREATE PROCEDURE dbo.spS_UserName(
@LOGIN VARCHAR(30))
AS
SET NOCOUNT ON
DECLARE @sql VARCHAR(300)
SET @sql = '
SELECT nombre
FROM OPENQUERY(linkedServer, ''
SELECT lastname + '''', '''' + name ...
Once you understand the BITs, all the pieces come together ![]()
March 3, 2004 at 1:44 pm
I just looked further down on the http://dictionary.reference.com/search?q=deprecated page and there it is... deprecated
Said of a program or feature that is considered obsolescent
and in the process of being phased...
Once you understand the BITs, all the pieces come together ![]()
March 2, 2004 at 1:03 pm
I think the German to English messed up... or maybe just the German to "American" ?
Check out http://dictionary.reference.com/search?q=deprecated ... this is what I was thinking when I read what you had...
Once you understand the BITs, all the pieces come together ![]()
March 2, 2004 at 12:54 pm
I just want to know the German word for "deprecated"
, just so i know what it means from now on.
I've been on the...
Once you understand the BITs, all the pieces come together ![]()
March 2, 2004 at 12:33 pm
After Frank posted about using a Jobs, the original poster asked "is there any other way through coding?", so I put in my 2 cents about being able to T-SQL...
Once you understand the BITs, all the pieces come together ![]()
March 2, 2004 at 11:11 am
I agree with the idea that a Job is most likely the best method. This can be done in code fairly easily (4 or 5 T-SQL statements), and the Job...
Once you understand the BITs, all the pieces come together ![]()
March 2, 2004 at 7:13 am
Pat,
I did not look at it very closely, but I see that you have an OUTER JOIN on [glossary], with an ON condition that removes PHYSICIANS. Since and PHYSICIANS records...
Once you understand the BITs, all the pieces come together ![]()
March 1, 2004 at 9:14 am
Just saw your post Dan... here's a little snippet from some of the code I use. You'll have to fill in the @ vars, but it might be helpfull
Create Table...
Once you understand the BITs, all the pieces come together ![]()
February 27, 2004 at 3:16 pm
Well I ended up using an SP I wrote a while back that consists of creating a Job, executing it, monitoring its success or failure, and returning any error. Since...
Once you understand the BITs, all the pieces come together ![]()
February 27, 2004 at 9:02 am
Thanks Noel...
select
Case Status & (4+8)
When 0 Then 'FULL'
When 4 Then 'BULK_LOGGED'
When 8 Then 'SIMPLE'
End as RecoveryModel,
*
from Master..SysDatabases
Once you understand the BITs, all the pieces come together ![]()
February 26, 2004 at 11:04 am
Thanks Allen, this works perfect for me.
BTW, is the setting in a System table anywhere?
Once you understand the BITs, all the pieces come together ![]()
February 26, 2004 at 7:43 am
Viewing 15 posts - 46 through 60 (of 363 total)