Viewing 15 posts - 10,396 through 10,410 (of 18,926 total)
In case you missed that message?!?!
I'd really like to have those answers.
January 9, 2007 at 9:29 am
Can you print the @string command and post it here?
What error are you getting when executing?
January 9, 2007 at 9:24 am
Can we know the rest of the process? I'm not sure you are using the right tool for the job.
January 9, 2007 at 9:21 am
Have you tried with '1' instead of 1?
Also check the execution plan for implicit_conversion which would confirm vladan's theory.
January 9, 2007 at 9:19 am
And run the job every 2 minutes at least so that at most there is a 6m59s delay before the queuing and execution.
January 9, 2007 at 9:13 am
Dev server??
DBCC FREEPROCCACHE
Now you can search these forums for parameter sniffing to get more info on that topic.
January 9, 2007 at 9:12 am
I wouldn't expect any problems with that approach (without fully knowing your system).
Now to conclude... You only backup daily (I do too but with trans backups every 30 minutes >> we...
January 9, 2007 at 9:08 am
I don't see why this would be a problem (aside from creating a bug in the web application).
The real problem here is why do you backup only once a month?!?!?!
Can...
January 9, 2007 at 8:20 am
Sorry but I don't know the answer to that one... I guess we'll know at the same time.
But if I were you I'd keep reading those articles... they'll come in...
January 9, 2007 at 8:18 am
NOT NULLS means that the column is not nullable. If there already is data in the table and you need to add a non nullable column, then you have to...
January 9, 2007 at 8:16 am
ALTER TABLE dbo.TableName
ADD ColName INT NOT NULL /*optional from here*/ CONSTRAINT DF_TableName_Init DEFAULT (0)
January 9, 2007 at 7:41 am
You got a little bit of reading ahead but it's really worth it, for everyone involved.
January 9, 2007 at 7:39 am
We can't answer this type of question without having the tables ddl (with indexes and keys) along with the query and execution plan. ONce you provide that we'll most likely...
January 9, 2007 at 7:00 am
Add an sql step at the end of the first job and type in this line :
exec msdb.sp_start_job @job_name = 'jobname'
That will start the 2nd job.
January 9, 2007 at 6:35 am
Now that would be an interesting test... Count the recompiles of each execution plans.
Anyone got time to set this one up?
January 9, 2007 at 5:59 am
Viewing 15 posts - 10,396 through 10,410 (of 18,926 total)