June 10, 2016 at 4:50 am
ThomasRushton (6/10/2016)
Am I being unreasonable in now thinking "perhaps you're not the one who should be doing this"?
I'm going to say Yes only because DB Mail is incredibly confusing the first few times it gets set up. Miss one tiny little step or do it in the wrong order and anyone could spend hours / days trying to figure out what went wrong.
June 10, 2016 at 5:04 am
Brandie Tarvin (6/10/2016)
ThomasRushton (6/10/2016)
Am I being unreasonable in now thinking "perhaps you're not the one who should be doing this"?I'm going to say Yes only because DB Mail is incredibly confusing the first few times it gets set up. Miss one tiny little step or do it in the wrong order and anyone could spend hours / days trying to figure out what went wrong.
That was my feeling. It took quite a few attempts to get that small chunk of script working. I must have read half a dozen blog posts on the subject, as well as examined the code generated automatically before getting it down to "just" the code in the answer there.
Thomas Rushton
blog: https://thelonedba.wordpress.com
June 10, 2016 at 5:07 am
ThomasRushton (6/10/2016)
Brandie Tarvin (6/10/2016)
ThomasRushton (6/10/2016)
Am I being unreasonable in now thinking "perhaps you're not the one who should be doing this"?I'm going to say Yes only because DB Mail is incredibly confusing the first few times it gets set up. Miss one tiny little step or do it in the wrong order and anyone could spend hours / days trying to figure out what went wrong.
That was my feeling. It took quite a few attempts to get that small chunk of script working. I must have read half a dozen blog posts on the subject, as well as examined the code generated automatically before getting it down to "just" the code in the answer there.
Wait. Are you talking about you or the OP?
I thought you were talking about the OP.
June 10, 2016 at 5:48 am
Brandie Tarvin (6/10/2016)
ThomasRushton (6/10/2016)
Brandie Tarvin (6/10/2016)
ThomasRushton (6/10/2016)
Am I being unreasonable in now thinking "perhaps you're not the one who should be doing this"?I'm going to say Yes only because DB Mail is incredibly confusing the first few times it gets set up. Miss one tiny little step or do it in the wrong order and anyone could spend hours / days trying to figure out what went wrong.
That was my feeling. It took quite a few attempts to get that small chunk of script working. I must have read half a dozen blog posts on the subject, as well as examined the code generated automatically before getting it down to "just" the code in the answer there.
Wait. Are you talking about you or the OP?
I thought you were talking about the OP.
I thought so too. They can be a little confusing the first time, but the OP not knowing about 'show advanced options' was a flag for me. I hope they get it right and also understand it.
June 10, 2016 at 6:10 am
<<snip - dupe>>
Thomas Rushton
blog: https://thelonedba.wordpress.com
June 10, 2016 at 6:11 am
Ed Wagner (6/10/2016)
Brandie Tarvin (6/10/2016)
Wait. Are you talking about you or the OP?I thought you were talking about the OP.
I thought so too. They can be a little confusing the first time, but the OP not knowing about 'show advanced options' was a flag for me. I hope they get it right and also understand it.
I was talking about the OP. That was exactly what caused me to wonder...
Thomas Rushton
blog: https://thelonedba.wordpress.com
June 10, 2016 at 6:40 am
ThomasRushton (6/10/2016)
Ed Wagner (6/10/2016)
Brandie Tarvin (6/10/2016)
Wait. Are you talking about you or the OP?I thought you were talking about the OP.
I thought so too. They can be a little confusing the first time, but the OP not knowing about 'show advanced options' was a flag for me. I hope they get it right and also understand it.
I was talking about the OP. That was exactly what caused me to wonder...
Okay. Just making sure. Because your second post made me wonder if you had been talking about your response, which I thought was fine.
June 10, 2016 at 7:07 am
Brandie Tarvin (6/10/2016)
ThomasRushton (6/10/2016)
Am I being unreasonable in now thinking "perhaps you're not the one who should be doing this"?I'm going to say Yes only because DB Mail is incredibly confusing the first few times it gets set up. Miss one tiny little step or do it in the wrong order and anyone could spend hours / days trying to figure out what went wrong.
It depends. In my case, I'm sure I shouldn't be doing that. That's because there are system DBAs (jrs and Srs) that must authorize it and I've never configure db mail or any other smtp service. If he's the only one in his company, then there's no option.
June 10, 2016 at 7:11 am
Luis Cazares (6/10/2016)
Brandie Tarvin (6/10/2016)
ThomasRushton (6/10/2016)
Am I being unreasonable in now thinking "perhaps you're not the one who should be doing this"?I'm going to say Yes only because DB Mail is incredibly confusing the first few times it gets set up. Miss one tiny little step or do it in the wrong order and anyone could spend hours / days trying to figure out what went wrong.
It depends. In my case, I'm sure I shouldn't be doing that. That's because there are system DBAs (jrs and Srs) that must authorize it and I've never configure db mail or any other smtp service. If he's the only one in his company, then there's no option.
If he's the only one in his company, then his level of understanding is a bit frightening. The 'show advanced options' is a simple one that (I hope) any DBA would know.
June 10, 2016 at 7:24 am
ThomasRushton (6/10/2016)
Am I being unreasonable in now thinking "perhaps you're not the one who should be doing this"?
Not at all. They are clearly so far over their heads they can't see the surface anymore.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
June 10, 2016 at 7:44 am
Brandie Tarvin (6/9/2016)
Y.B. (6/9/2016)
So what do you say when your boss announces in a meeting that 'we' should look into NoSQL? No really...what do you say?I realize that there are good use cases for both NoSQL and traditional RDBMS but when your whole knowledge base is in one area, it kind of feels like a gut punch. Oh well, I guess I ought to spin up a Linux instance on Azure and start playing (learning).
That is a good question. Where does one even start to look into NoSQL?
Again, seriously. Because I've pretty much ignored all the NoSQL stuff on account of not currently using it at work.
One way to explore this is to look at data sets that aren't necessarily relational. For example, event logs can be injected into Mongo pretty easily. Any data where you don't necessarily have a fixed schema on write is a good candidate; so maybe external data sources that you need to on-board.
Need to persisting payloads from API calls but parsing them on write to map them to your relational model is difficult/expensive? Again, Mongo is perfect for this.
If you're using a SQL Server column to store XML or (especially) JSON you may want to look into a non-relational document store (though it looks like 2016 has some nice JSON functionality).
Another example, might be using ElasticSearch for fuzzy/full-text searching (ES is really a document store under the hood).
If these data sets have keys that reference objects in your relational model, the data "joining" would be handled on read - so you need a middle tier that can handle it.
One plus for most NoSQL systems is that they are generally easier to scale horizontally than MS SQL, so if you have a system that is heavy on reads and needs scalability (e.g. a search engine), modeling that in something non-relational might be a win.
My org is keeping an open mind about NoSQL though all of our core systems remain firmly relational. We have committed heavily to ElasticSearch as our search engine.
June 10, 2016 at 8:56 am
And some of us thought the Microsoft certification process was debt-heavy. Glad none of us have to do this.
June 10, 2016 at 8:57 am
Steve Thompson-454462 (6/10/2016)
Brandie Tarvin (6/9/2016)
Y.B. (6/9/2016)
So what do you say when your boss announces in a meeting that 'we' should look into NoSQL? No really...what do you say?I realize that there are good use cases for both NoSQL and traditional RDBMS but when your whole knowledge base is in one area, it kind of feels like a gut punch. Oh well, I guess I ought to spin up a Linux instance on Azure and start playing (learning).
That is a good question. Where does one even start to look into NoSQL?
Again, seriously. Because I've pretty much ignored all the NoSQL stuff on account of not currently using it at work.
One way to explore this is to look at data sets that aren't necessarily relational. For example, event logs can be injected into Mongo pretty easily. Any data where you don't necessarily have a fixed schema on write is a good candidate; so maybe external data sources that you need to on-board.
Need to persisting payloads from API calls but parsing them on write to map them to your relational model is difficult/expensive? Again, Mongo is perfect for this.
If you're using a SQL Server column to store XML or (especially) JSON you may want to look into a non-relational document store (though it looks like 2016 has some nice JSON functionality).
Another example, might be using ElasticSearch for fuzzy/full-text searching (ES is really a document store under the hood).
If these data sets have keys that reference objects in your relational model, the data "joining" would be handled on read - so you need a middle tier that can handle it.
One plus for most NoSQL systems is that they are generally easier to scale horizontally than MS SQL, so if you have a system that is heavy on reads and needs scalability (e.g. a search engine), modeling that in something non-relational might be a win.
My org is keeping an open mind about NoSQL though all of our core systems remain firmly relational. We have committed heavily to ElasticSearch as our search engine.
Thanks for the reply.
I wonder... Our reporting team has a database where they essentially flatten all our data into giant tables so their reports read quicker. Would this be a candidate for a NoSQL solution?
June 10, 2016 at 9:29 am
Brandie Tarvin (6/10/2016)
Thanks for the reply.
I wonder... Our reporting team has a database where they essentially flatten all our data into giant tables so their reports read quicker. Would this be a candidate for a NoSQL solution?
I think it could be; it would depend on the downstream system generating the reports - can it consume/parse JSON-like data? There are plenty of reporting stacks that work with NoSQL stores; for example, Kibana for ElasticSearch.
If the data you are flattening has a variable schema (e.g. sometimes columns are missing, sometimes new columns are added, etc.), document stores will happily accept this at write, so that might be a nice value add. Then it would be up to the reporting client to manage the data (e.g. come up with a new binding for the new column).
June 10, 2016 at 10:02 am
Brandie Tarvin (6/9/2016)
Y.B. (6/9/2016)
So what do you say when your boss announces in a meeting that 'we' should look into NoSQL? No really...what do you say?I realize that there are good use cases for both NoSQL and traditional RDBMS but when your whole knowledge base is in one area, it kind of feels like a gut punch. Oh well, I guess I ought to spin up a Linux instance on Azure and start playing (learning).
That is a good question. Where does one even start to look into NoSQL?
Again, seriously. Because I've pretty much ignored all the NoSQL stuff on account of not currently using it at work.
What's NoSQL? Key value database? Document database? Graph database? There are lots of choices here.
I think it's good to learn a bit about them. Where they work, and where they don't.
Viewing 15 posts - 54,541 through 54,555 (of 66,738 total)
You must be logged in to reply to this topic. Login to reply