Viewing 15 posts - 181 through 195 (of 530 total)
There should be no difference between Query Analyzer and your Perl script. Are you sure there is no condition in the trigger that is not satisfied?
August 12, 2003 at 4:20 am
If the ODBC driver doesn't do the job, you could export to a csv and do the import from an agent in Notes that you've scheduled.
August 11, 2003 at 6:19 am
Don't know about encryption for SQL Server, but you could use a VPN tunnel to make sure all data passing is encrypted.
August 6, 2003 at 7:16 am
If you use the ALTER TABLE technique, be aware that any other inserts taking place (by another user, for example) will also not fire the trigger!
August 6, 2003 at 7:14 am
I am afraid I can't really help you on this. We have used UDT's in some projects (using VB.NET), but we did not have a direct link to the type...
August 6, 2003 at 6:53 am
To get a list of all records that do not have matching records, use the following query:
SELECT dlo.DIVISON_CD, dlo.GROUP_TXT,
SC60.DIVISON_CD...
August 4, 2003 at 7:40 am
This is normal behaviour for a trigger.
Inside the trigger, you have a 'inserted' and 'deleted' table. These tables contain the complete set that was changed during the update ('deleted' contains...
August 1, 2003 at 8:28 am
I don't think you can do that.
A work around is doing the calculation in the from clause. Something along the lines of
SELECT Calc_Field, <other fields>
FROM (SELECT <other fields>, <Calculated Field>...
July 31, 2003 at 8:58 am
You can do this in one query, without the need for temp tables :
SELECT H.sh_serial_no,
Mini.Invoice_Date, Mini.Meter,
...
July 31, 2003 at 8:55 am
Antares,
I can agree with what you are saying in your post. A 'simple' processing UDF should not incur a large overhead.
However, I'm not clear on how the performance is affected...
July 31, 2003 at 5:47 am
Or continue to use the join syntax as in:
UPDATE Table1
SET Table1.NumOfImages = temp1.NumOfImages
FROM Table1
INNER JOIN
(SELECT KeywordID, count(*) as NumOfImages
...
July 31, 2003 at 5:39 am
I tend to keep away from UDF's if at all possible. It is a great feature to reuse code, but it can kill performance as you noticed.
One place we 'often'...
July 31, 2003 at 2:52 am
Jeremy,
If performance really is too slow, drop the Userdefined functions and code everything directly in the SQL Statement.
If you want, you can testdrive, only doing the updates of the function...
July 30, 2003 at 8:32 am
There is another 'SQL language' around that is designed specifically for querying cubes. It is called MDX (Multi-Dimensional Expressions, if I recall correctly). You can use that to query your...
July 30, 2003 at 8:02 am
You can use the BCP command line utility to import and export data to a (formatted) file. Not exactly T-SQL of course, but using xp_cmdshell it is possible.
I think you...
July 30, 2003 at 5:36 am
Viewing 15 posts - 181 through 195 (of 530 total)