Hi Ales, Thank you for providing such a detailed description of your circumstances, and I can see how the DB_OPERATION limit can be a problem. The core engineering team is aware that this limit makes certain types of activities difficult (such as starting or restructuring an account) and they are investigating potential solutions. Unfortunately I don't have any other information at this time, but thank you again for the feedback.
Best, - Eric On Oct 7, 7:13 am, Ales Sturala <[email protected]> wrote: > Hello Eric, > txs for you time! Our application takes client's list of products and > loads it to the AdWords. Besides that if the product does not exist > anymore or something is changed (like a price) it changes the data in > AdWords. Therefore operations Add, Set and Remove are the only > important for us. Now imagine two real scenarious where we're having > troubles now: > > 1) new client comes and wants to load all ads and keywords for the > first time into adwords (I'm talking about 200.000 keywords for > example) => the API cannot handle so many requests now because of the > DB_Operation limit > 2) we change how the ads should look like, therefore all old ads are > deleted and all new have to be loaded => again we're getting into > DB_OPERATION troubles > > In the first case the limitation causes that only part of the data can > be loaded to AdWords and we have to wait till next day to load other > part. > In the second case it's even worst, imagine the account is live and we > decide to change the ad structure. Now all ads will be deleted, part > of new ads would be loaded and then we have to wait another day to > load rest of the ads (or even worse if the loading would require > several days). We're managing several accounts. Most of them contain > large amount of ads and keywords. > > One more questions to ask, do you take in account a size of the > account (e.g. amount of money spent by an account) or every account > has the same limitation, so small acount with few keywords has same > number of allowed database operations as an account having 200.000 > keywords? Because so far we're running the API 2009 only in sandbox > and there we use a special account that doesn't have any live > campaigns at all and is used only for testing purposes. > > Regards, > Ales > > On Oct 6, 11:11 pm, AdWords API Advisor <[email protected]> > wrote: > > > > > Hi, > > > The DB_OPERATION quota is only affected by mutate operations (ADD, > > SET, REMOVE), and so you should not run into this issue during read > > requests. Can you give me more technical detail about your > > application and when you are encountering this error? > > > Best, > > - Eric Koleda, AdWords API Team > > > On Oct 6, 5:14 am, Ales Sturala <[email protected]> wrote: > > > > Hello, > > > I'm wondering about the quota limitation used on sandbox. Is there any > > > information on the Internet about it? Is it possible to higher this > > > quota somehow? It's VERY VERY low now - it's not even enough to load > > > ads and keywords for particular client into adwords, getting the > > > database operation limit error! > > > > Is there anything we can do about it? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en -~----------~----~----~----~------~----~------~--~---
