![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Entry tags:
- busy,
- frustrated,
- geek,
- zombie
(no subject)
I've been working on this project for the better part of a year. Not continuously, but in fits and starts as new pieces of it fall into place. Earlier this year it was put on permanent hold while we waited for some programming changes to go in because a couple of critical fields weren't being fed in our database.
They completed testing and rolled out those changes about two months ago, but the next stumbling block was that I needed to combine queries from two different databases, and the tool they have given me does not let me do that. No problem, one of the programmers on staff set up some aliases and links to bring that data over in a form that I could use. That took about a month and a half.
Unfortunately the first time I tried to use this new dataset the whole thing blew up around my ears when I ran a query. I had a hunch that it was something to do with the way the tables were linked, and I sent off a note to the project head saying as much. He wrote back saying that I couldn't do the query because the tables were linked table1-->table2-->tabler3-->table4, and thus my query that pulled in data from tables1 and 4 simultaneously wouldn't work. Hope this helps. Have a nice day.
I fired back a letter to all concerned where I was perhaps a bit more acerbic than I meant to be, stating that while it was nice to have table4 in place, I could have fetched that data myself with a separate query, and that unless the linking was fixed so that I could do simultaneous queries, I was back to square zero. Square zero meant that we might have to consider our other options again (such as dedicated hardware).
To my surprise, the programmer called me yesterday and said, "Since you're the end user, maybe you could tell me exactly how you want these tables linked..." I told him, and this morning he sent me an email saying, "OK, try it now." What do you know - it works! After nearly a year of delays I can finally get started on...
Ack! Ten minutes later my boss called an impromptu meeting and pulled me temporarily off the project so that I can work on a more pressing one. In short, this project is now on hold unless the stakeholders begin to scream really loud for it.
They completed testing and rolled out those changes about two months ago, but the next stumbling block was that I needed to combine queries from two different databases, and the tool they have given me does not let me do that. No problem, one of the programmers on staff set up some aliases and links to bring that data over in a form that I could use. That took about a month and a half.
Unfortunately the first time I tried to use this new dataset the whole thing blew up around my ears when I ran a query. I had a hunch that it was something to do with the way the tables were linked, and I sent off a note to the project head saying as much. He wrote back saying that I couldn't do the query because the tables were linked table1-->table2-->tabler3-->table4, and thus my query that pulled in data from tables1 and 4 simultaneously wouldn't work. Hope this helps. Have a nice day.
I fired back a letter to all concerned where I was perhaps a bit more acerbic than I meant to be, stating that while it was nice to have table4 in place, I could have fetched that data myself with a separate query, and that unless the linking was fixed so that I could do simultaneous queries, I was back to square zero. Square zero meant that we might have to consider our other options again (such as dedicated hardware).
To my surprise, the programmer called me yesterday and said, "Since you're the end user, maybe you could tell me exactly how you want these tables linked..." I told him, and this morning he sent me an email saying, "OK, try it now." What do you know - it works! After nearly a year of delays I can finally get started on...
Ack! Ten minutes later my boss called an impromptu meeting and pulled me temporarily off the project so that I can work on a more pressing one. In short, this project is now on hold unless the stakeholders begin to scream really loud for it.
no subject
no subject
*ACK!*