topic index issue in Application Development and Automation Discussions

index issue

Madhurivs23 — Sat, 22 Sep 2007 05:19:13 GMT

Hello,

I have created an index on one table and not transported it on the quality. but the request is generated , now i want to delete that index . if i delete that index from se14, then will the deletion get saved in the same request?

if yes then if i delete that request , whether it will create any problem while changing that table in the future?

thanks

rgds

Madhuri

Re: index issue

Former Member — Sat, 22 Sep 2007 13:56:05 GMT

You cant add changes to released transport requests.I dont see any issues by deleating this index.

Thanks

Prince Jose

Re: index issue

Former Member — Sun, 23 Sep 2007 03:02:59 GMT

So long as you have not released it, the change will be saved in the same request.

Rob

Re: index issue

Former Member — Sun, 23 Sep 2007 06:07:27 GMT

Hi Madhuri

if you delete an index from that , there is no problem with that , that won't be stored under that request it will be completely deleted from that

suppose if you want to delete total request then it becomes a problem

so you can delete that index directly

reward if usefull

Re: index issue

Madhurivs23 — Mon, 24 Sep 2007 07:13:16 GMT

the current status is like this:

step 1)index zv created.

step 2)the request of creation of index is not released yet. <b>eg req123</b>

now, I want to do this.,

step 3)delete the index zv, ( so it will get saved in the same request)

step 4)delete the request req123.

now, if I do the step 4, then will it create any problem while changing that table in future.(adding some fields etc.)

Re: index issue

Former Member — Mon, 24 Sep 2007 08:10:06 GMT

Hi Madhuri,

first delete the index from that request.....and then just delete the index from that table thats all...

hope it may not cause any problem...

please reward incase usefull...

regards,

prashant

Re: index issue

Former Member — Mon, 24 Sep 2007 11:04:04 GMT

Hi,

Any way u created first time the index under the new request which it means if u delete the index from that request it wont save means it doesnt contain any thing under request reg index.

Suppose if you delete any thing which it aleady there in production/quality/development server, those changed only saved under new request, normally this will happends in supporting projects.

But in your case u only created index, So first you have to delete index under request and then goto table and delete the index.

i am not sure to delete request directly is good, so better to ask the basis guys before deleting request.

<b>Reward with points if helpful.</b>

Regards,

Vijay

Re: index issue

Madhurivs23 — Mon, 24 Sep 2007 11:15:20 GMT

if i do upto step 3, and do not delete the request and keep it as it is.

then if suppose somebody make any changes to that table and create the new request,

then will there be any impact of my request over the newly created request?

and suppose that other person want to transport his request in quality, will my request create any problem?

Re: index issue

Former Member — Mon, 24 Sep 2007 13:32:17 GMT

All you have to do is delete the index and then release the transport. Further changes will be to the table without the index and in a new request.

Rob

Re: index issue

Former Member — Thu, 27 Sep 2007 12:05:35 GMT

Hello,

Just Follow these steps if you dont want this index

1. delete this index.

2. while deleting this this index save the changes in the same request.

3. you dont want changes made by you to be transported then delete request created.