Viewing 15 posts - 1 through 15 (of 39 total)
When it comes to hard-coding datetime values, there is one format that will always work - regardless of any of the settings on the datebase: 'YYYYMMDD'. This is the recommended...
February 10, 2005 at 1:49 pm
Interesting situation...
I think I remember having experienced that EM table properties shows the wrong rowcount. The information shown there is based on the statistics available, and not on the actual...
February 10, 2005 at 11:50 am
I agree that Gordon's Google-based solution have problems when the collation is case insensitive, but why not force the collation to be case-sensitive just for the statement?
Replace displayName with (displayName...
February 9, 2005 at 3:13 pm
In addition to those mentioned above:
"Select into" is one of the bulk-loading methods available in SQLServer, and will therefore follow a slightly different & simpler logging model than "insert into". This...
February 9, 2005 at 10:34 am
Hi,
There definitely seems to be a problem obtaining the identity value through a linked server. Hopefully there are somebody out there who knows a good solution, but if you...
February 7, 2005 at 1:39 pm
Hi,
There's a setting that regulates whether a trigger will be called recursively or not: RECURSIVE_TRIGGERS
If you allow recursive triggers, it will not necessarily end up in a dead-lock; more likely...
February 7, 2005 at 7:30 am
Hi,
A couple of other differences:
Functions can't alter the state of the database, only retrieve data or perform calculations.
Procedures can, i.e. update, inserts and deletes are allowed.
Functions can be used...
February 6, 2005 at 7:07 am
As a follow up to the security suggestion: There is a user option called xact_abort that may have a different setting for different credentials. This is used to indicate the...
October 21, 2004 at 12:25 pm
Thanks for the input. I believe we also use SP3, but I'll check if we have the latest update available. Could very well be that there is some versioning or...
October 21, 2004 at 10:49 am
I feel that the answer 4 is insufficient, when it doesn't consider the ANSI_WARNINGS-setting. The error may be caused by ANSI_NULLS, but it could equally have been caused by ANSI_WARNINGS? More correct...
October 5, 2004 at 3:14 pm
I would guess that the problem is databinding in the .NET-application rather then the procedure. But the procedure is not easy to handle, as there are no defined output-parameters - the...
October 5, 2004 at 2:27 pm
Hi,
We use dynamic SQL a lot, and find it a very useful tool for many purposes. The article mentioned above is however very useful reading - it is absolutely good...
October 5, 2004 at 11:55 am
You could try one of these methods after each filter in the batch, and see if that's what you're looking for:
select @@rowcount as 'Filter-name'
or
October 3, 2004 at 5:57 am
Could the full-error message be something like this?
Server: Msg 8115, Level 16, State 8, Line 8
Arithmetic overflow error converting numeric to data type numeric.
If so, it is probably...
October 1, 2004 at 8:41 am
Hi,
Have had quite a bit of struggle with these settings myself. I thought I'd just mention a few things that you may or may not be aware of:
- Both ANSI-settings...
September 30, 2004 at 2:54 pm
Viewing 15 posts - 1 through 15 (of 39 total)