Viewing 15 posts - 91 through 105 (of 146 total)
Hi here is the SP I run and the execution plan of the code only run hope it helps. Please let me know if you need more information.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Do not reinvent the wheel.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
February 3, 2010 at 11:07 pm
Thanks for all the help so far. When I try to get an estimate execution plan on just the code it gives me this error:
Msg 208, Level 16, State 0,...
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Do not reinvent the wheel.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
February 3, 2010 at 10:37 pm
I did create a new sp under new name with recompile. This did exactly the same. Even trying to get estimated execution plan on the sp runs more than and...
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Do not reinvent the wheel.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
February 3, 2010 at 2:09 am
Yesterday afternoon I got the SP to run in 1 min by substituting one of the join with temp table. This works fine but what I do not understand is...
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Do not reinvent the wheel.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
February 2, 2010 at 10:58 pm
the log file is under th log directory but is not displayed by SQL log viewer.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Do not reinvent the wheel.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
February 2, 2010 at 10:52 pm
example
exec sp_temp - this times out
code from sp -
select * from t1
join viewa on a=b
join t2 on c=d
this executes in 30 sec
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Do not reinvent the wheel.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
February 2, 2010 at 4:03 am
Forgot to mention that the physical file has data in it.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Do not reinvent the wheel.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
January 29, 2010 at 1:58 am
There is different types of audit. what do you whish to get from the audit data?
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Do not reinvent the wheel.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
January 29, 2010 at 1:41 am
I have had the same problem that it fails but it was always intermediate. Some systems will safe correctly and some not. The systems that it worked on is sql...
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Do not reinvent the wheel.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
January 18, 2010 at 6:08 am
It is a risk if you have someone that wants to be milicious, he can steel information or remove important data that will cost you time and man hours to...
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Do not reinvent the wheel.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
January 18, 2010 at 5:10 am
Hi
I have seen these manual encryption procedures but why would you want to use it. It is going to cost alot of work to get it working and maintain it....
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Do not reinvent the wheel.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
January 18, 2010 at 4:50 am
You can use the following to check where you duplicate records is.
select d.vcrEmployeeSignOff,
d.vcrManagerSignOff,
d.vcrSendForReviewSelfAssessment,
d.vcrManagerReviewSignOff,
d.vcrSelfReviewSignOff,
d.vcrComnMgrSignOff,
d.vcrCommEmployeeSignOff,
d.vcrCommSkipMgrSignOff,
d.vcrCommHRFeed,
d.vcrCommSendToTM,
d.vcrpriority,COUNT(*) from tblstatusmaster d
group by --c.vcrSendForReviewGoals = d.vcrSendForReviewGoals and
d.vcrEmployeeSignOff,
d.vcrManagerSignOff,
d.vcrSendForReviewSelfAssessment,
d.vcrManagerReviewSignOff,
d.vcrSelfReviewSignOff,
d.vcrComnMgrSignOff,
d.vcrCommEmployeeSignOff,
d.vcrCommSkipMgrSignOff,
d.vcrCommHRFeed,
d.vcrCommSendToTM,
d.vcrpriority
having ,COUNT(*) > 1
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Do not reinvent the wheel.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
January 18, 2010 at 4:40 am
This sounds like a problem with AD security that changed or maybe a group (normally the local\administrators) that was removed disabled on the SQL instance or server security.
What happens...
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Do not reinvent the wheel.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
January 18, 2010 at 4:22 am
The reason for the maint plan not working is that the pointer to the deleted database is saved in the package and not automaticaly updated. As mentioned you can just...
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Do not reinvent the wheel.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
January 18, 2010 at 4:03 am
This is a problem with SQL 2000 SP upgrade. What SP are you using on the SQL2000 server. To fixe run the following scripts Instcat.sql on the 2000 server. For...
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Do not reinvent the wheel.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
January 18, 2010 at 3:56 am
Viewing 15 posts - 91 through 105 (of 146 total)