Viewing 15 posts - 211 through 225 (of 530 total)
ISNULL works exactly the same for a nvarchar data type. Maybe you can post some more info to help us troubleshoot your problem.
Post the query you use and some sample...
July 19, 2003 at 2:44 pm
If I where in your shoes, I would stick with the current method of storing files on the filesystem and indexing stuff in the database. In the end, that's what...
July 19, 2003 at 1:44 pm
You have two possibilities. The first one is using IF statements, each with their own query. This is OK if you only have a few parameters, but the number of...
July 19, 2003 at 1:40 pm
Shouldn't be a problem to store blobs in the database if it is 'only' 1GB worth of data (even a terabyte is possible). However, I don't see how storing the...
July 18, 2003 at 3:56 pm
Like Brians solution better. We used to do that in one of our projects.
A mainframe would put a bunch of files on our system, and then write the 'DONE' file.
Problem...
July 18, 2003 at 3:47 pm
Frank, thanks for the explaining, I'll use the smiley on myself this time ...
July 18, 2003 at 9:13 am
If I understand the meaning of DSUM correctly, you should use a GROUP BY clause.
With
DSum(expr, domain, criteria)
, the query would look like
SELECT...
July 18, 2003 at 7:29 am
Another way might be to have an 'UpdateScripts' table that stores your script.
You can upload your script using a webinterface and store it in SQL Server.
Then, you run a job...
July 18, 2003 at 2:13 am
I have a pretty good idea what you're after.
I guess you make one big, giant T-SQL script to upgrade your database from one version to the other. (We do that...
July 17, 2003 at 2:33 pm
Second that. If you can't join on the TOP 3000, try to rewrite it as an EXISTS clause. That should be faster than an IN statement.
If you still end up...
July 17, 2003 at 2:25 pm
Don't see the problem here... If the Manager gets deleted, so would the ID, so there is no difference in it.
I personnaly would go for :
1. Track ID's using a...
July 17, 2003 at 9:56 am
You're well underway of building a complete solution. But I guess you'll have to use a table to store your results (can be a temporary one). If you are sure...
July 17, 2003 at 9:52 am
As the article points out, you can't do this in a single query. You'll have to resort to using a cursor in a stored procedure.
July 17, 2003 at 8:12 am
An alternative to delete all those records is
DELETE MyTable
FROM MyTable t1 INNER JOIN MyTable t2
ON t1.Unique_ID = t2.Unique_ID
AND t1.DateField...
July 17, 2003 at 4:53 am
You can use the following query.
DELETE FROM MyTable
WHERE Unique_ID = <ID to Delete>
AND DateField = (SELECT min(t1.DateField)
...
July 17, 2003 at 4:49 am
Viewing 15 posts - 211 through 225 (of 530 total)