Viewing 15 posts - 991 through 1,005 (of 1,186 total)
I have run into something similar in the past and had to increase the job history log. Please see below
June 17, 2004 at 5:35 am
You will need to put the
select QTY_PO from @tablename where PO_ID = '12345-000'
into a variable and then run EXEC sp_executesql @var for the @var for tablename to work. I hope...
June 16, 2004 at 5:43 pm
I don't think that TSQL will do it because that just controls the behavior of the data and server not the QA tool ...
June 16, 2004 at 5:11 am
Try running the query and display the results in text (my preferred DEFAULT) vs. grid. This can be changed in Query > Results in Text (for current session) or permanently...
June 16, 2004 at 5:09 am
Why not just review sysjobhistory table via QA???
June 10, 2004 at 4:55 pm
an alternative is to run sp_change_users_login (can look it up in BOL) and this should fix it too...
June 10, 2004 at 12:10 pm
Another thing you might need to do is re-visit all of your users to make sure that they are not orphaned
(due to the detach, copy, re-attach) from a different...
June 10, 2004 at 10:08 am
How about creating 3 variables
@filepath and @filename, @ActionCmd
set @filepath = the file path information from your sysprefs table
set @filename = the filename information from your files table
set @ActionCmd = 'DEL '...
June 10, 2004 at 10:03 am
Here is some sample code for you
CREATE TABLE tblTest
([Field1] CHAR(10) NULL) ON [PRIMARY]
ALTER TABLE [tblTest] ADD
CONSTRAINT [DF_tblTest_Field1] DEFAULT ('Hi') FOR [Field1]
GO
sp_help tblTest
June 10, 2004 at 5:36 am
This might help...
DECLARE @Int INTEGER
DECLARE @Var CHAR(6)
DECLARE @Pad VARCHAR(6)
SET @Int = 12
SET @Pad = REPLICATE(0, (6 - LEN(@Int)))
SET @Var = CAST(@Pad AS VARCHAR) + CAST(@Int AS VARCHAR)
PRINT '''' + @Var...
June 10, 2004 at 5:27 am
What you will probably end up doing is building a variable that has all the information in it and then use xp_cmdshell to initiate it:
DECLARE @Var NVARCHAR(255)
SET @Var = 'backup...
June 9, 2004 at 6:16 am
I honestly don't know. It looks to me like the regional setting automatically uses case sensitivity??? There may be a way of overriding the individual settings but it is going...
June 8, 2004 at 4:48 pm
Clunky I know but this should work
DECLARE @Var INT
SET @Var = (SELECT ROUND(18.50, 0) + 5)
SELECT
CASE WHEN @Var >= 0 AND @Var <= 5 THEN 5
WHEN @Var >...
June 8, 2004 at 12:07 pm
Check
SELECT * FROM ::fn_helpcollations() WHERE [name] LIKE '%hungarian%'
Looks like you are having some sort of case sensitive collation issue with Hungarian
June 8, 2004 at 9:10 am
Viewing 15 posts - 991 through 1,005 (of 1,186 total)