Viewing 15 posts - 10,591 through 10,605 (of 18,923 total)
Ya that's one way to go. But this error is severe because it's not something that should happen. If you want to insert a tinyint into a column, then you...
December 13, 2006 at 1:26 pm
Also the use of a stored proc would completely void the need for this :
CREATE PROCEDURE dbo.Demo @LastName AS VARCHAR(30), @CustID AS VARCHAR(10)
AS
SET NOCOUNT ON
UPDATE dbo.Customers SET Last_name =...
December 13, 2006 at 1:20 pm
Double the quotes (2 single quotes >> 2 characters) :
UPDATE Customers SET Last_Name = 'O''CONNOR' WHERE Cust_ID = 'A34778
December 13, 2006 at 1:18 pm
"I didn't know about the SqlDataAdapter thing but it doesn't surprise me. I think M$ favours ease of use over good sense. For example, being able to put non-alphabetic...
December 13, 2006 at 1:16 pm
As I already said, this error is TOO SEVERE to be trapped in the sp like so (maybe in a nested proc but I would even doubt that).
create table t1(f1...
December 13, 2006 at 1:07 pm
I have never heard of it this way. I think you'd be better off to start a new thread so you get more exposure for this question. personnally I have...
December 13, 2006 at 10:02 am
I would tell you to use Ronald's version but it takes 5 times more time to run than my version on my system. I'll let you check out which version...
December 13, 2006 at 9:01 am
NP, normally I push harder to change the design or the aproach of the problem, but I don't think there's a way in this case. But I hope you can...
December 13, 2006 at 8:33 am
To finish Jeff's idea. You'd simply use a tally (numbers) table to increment a starting date placed in a variable. Then you'd simply left join that results to the current...
December 13, 2006 at 8:31 am
That's a very good point, however we need to find a specific value in the whole database. Sometime that this tool is not built to do
December 13, 2006 at 8:29 am
This solution is similar to the other one. Only 1 column is scanned per run. If this is acceptable in your situation then go with it, it'll work. But if...
December 13, 2006 at 8:28 am
The problem with this solution is that you will do a table / index scan for every column in each table. Here I have quite a few tables with over...
December 13, 2006 at 8:24 am
Have you tried something like :
SELECT @strSQL = N'SET @strCntOut = (SELECT count(*) FROM ' + @tabPName +
+ ' WHERE iID = ' + cast(@itemCounter as varchar(5))
+ ' AND vchBatchNo...
December 12, 2006 at 2:09 pm
Here's the first correction for the XType part :
SELECT XType, * FROM dbo.SysTypes
WHERE Collationid IS NULL AND XType NOT IN (173, 61, 34, 58, 98, 189, 36, 165)
Then...
December 12, 2006 at 1:02 pm
Viewing 15 posts - 10,591 through 10,605 (of 18,923 total)