March 16, 2017 at 4:19 pm
Comments posted to this topic are about the item Connect to MongoDB on Remote Linux Server with Powershell
March 19, 2017 at 4:52 pm
Good bit of research there. Thanks for sharing.
Of bigger concern to me is the whole nature of this task. If LINUX and MongoDB is so good (according to some), why is it the folks using those couldn't come up with the report(s) on the LINUX/MongoDB side of the house? Seems like that would have been the better/faster choice instead of dragging data from one server to another.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 20, 2017 at 4:51 am
Jeff Moden - Sunday, March 19, 2017 4:52 PMGood bit of research there. Thanks for sharing.
Of bigger concern to me is the whole nature of this task. If LINUX and MongoDB is so good (according to some), why is it the folks using those couldn't come up with the report(s) on the LINUX/MongoDB side of the house? Seems like that would have been the better/faster choice instead of dragging data from one server to another.
Hi Jeff,
Why is it you don't have your reportingservice running on your (production)databaseserver? 🙂 Mind you; you respons reads a little biased?
With SSRS already in place/actively used/comfortable with; that would be the logical choice for (just) a single datapoint (as I understood from the original article).
Ad-hoc implementations often grow sour on you. That "feature" is definitely "multiplatform"!
(Admirer of your work here btw!)
Regards!
@michael-2: Thanks for posting the script Allways great to be able to stand on the shoulders of guys ('n girls) bigger than me!
[/edit]; added thanks to orignal article and added bias-question 😉
[/edit2,3,4...] clarify!
March 20, 2017 at 8:41 am
fschreuder - Monday, March 20, 2017 4:51 AMJeff Moden - Sunday, March 19, 2017 4:52 PMGood bit of research there. Thanks for sharing.
Of bigger concern to me is the whole nature of this task. If LINUX and MongoDB is so good (according to some), why is it the folks using those couldn't come up with the report(s) on the LINUX/MongoDB side of the house? Seems like that would have been the better/faster choice instead of dragging data from one server to another.
Why is it you don't have your reportingservice running on your (production)databaseserver? 🙂 Mind you; you respons reads a little biased?
With SSRS in place/activly used; that would be the logical choice for a single datapoint (as I understood from the original post).
Ad-hoc implementations often grow sour on you. That is "multiplatform"!Regards!
Thanks for posting the script Michael! Allways great to be able to stand on the shoulders of guys ('n girls) bigger than me!
[/edit]; added thanks to orignal post and added bias-question 😉
Not sure but you may have quoted the wrong person on your response. The question does remain, though... if all of the data lives on MongoDB on a Linux server, why not do it there instead of dragging the data across to another system? Centralize reporting also leads to centralized single points of failure.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 20, 2017 at 8:51 am
Jeff Moden - Sunday, March 19, 2017 4:52 PMGood bit of research there. Thanks for sharing.
Of bigger concern to me is the whole nature of this task. If LINUX and MongoDB is so good (according to some), why is it the folks using those couldn't come up with the report(s) on the LINUX/MongoDB side of the house? Seems like that would have been the better/faster choice instead of dragging data from one server to another.
yes... the bigger concern is valid. So Dev is in India and Palo Alto and Ops is in Dallas. Lets just say, there is very little communication between the two. Dev likes to find shiny new toys to build new apps on. So at the time when they deployed this app, Mongo was the hot new DB, thus now we have Mongo in our Production environment. Trying to keep things positive it has exposed me to other technologies and expanded my skill set. It has also reinforced my fondness for SQL Server in the enterprise. With the open source movement, "free" isn't always "free". Just because it's "free" you still have to support it and most of the time its trying to find scripts, trolling community forums or develop you own process to manage this "free" database.
Michael
http://thesurfingdba.weebly.com/
March 20, 2017 at 9:07 am
fschreuder - Monday, March 20, 2017 4:51 AMJeff Moden - Sunday, March 19, 2017 4:52 PMGood bit of research there. Thanks for sharing.
Of bigger concern to me is the whole nature of this task. If LINUX and MongoDB is so good (according to some), why is it the folks using those couldn't come up with the report(s) on the LINUX/MongoDB side of the house? Seems like that would have been the better/faster choice instead of dragging data from one server to another.
Why is it you don't have your reportingservice running on your (production)databaseserver? 🙂 Mind you; you respons reads a little biased?
With SSRS in place/activly used; that would be the logical choice for a single datapoint (as I understood from the original post).
Ad-hoc implementations often grow sour on you. That is "multiplatform"!Regards!
Thanks for posting the script Michael! Allways great to be able to stand on the shoulders of guys ('n girls) bigger than me!
[/edit]; added thanks to orignal post and added bias-question 😉
My response is totally biased in favor or SQL Server vs Open Source solutions. "Free" isn't always "Free".. Basically my script is my ETL process to the data to a place where it is in a usable form. The nature of the task was to deliver to a manager a list of customers with the disaster recovery sku in place. I am providing my manger access to the table where this data lands. Didn't really see the need to get SSRS involved. He just wanted a way to track this info as we roll out upgrades to this app.
March 20, 2017 at 9:29 am
thedspaincrew - Monday, March 20, 2017 9:07 AMfschreuder - Monday, March 20, 2017 4:51 AMJeff Moden - Sunday, March 19, 2017 4:52 PMGood bit of research there. Thanks for sharing.
Of bigger concern to me is the whole nature of this task. If LINUX and MongoDB is so good (according to some), why is it the folks using those couldn't come up with the report(s) on the LINUX/MongoDB side of the house? Seems like that would have been the better/faster choice instead of dragging data from one server to another.
Why is it you don't have your reportingservice running on your (production)databaseserver? 🙂 Mind you; you respons reads a little biased?
With SSRS in place/activly used; that would be the logical choice for a single datapoint (as I understood from the original post).
Ad-hoc implementations often grow sour on you. That is "multiplatform"!Regards!
Thanks for posting the script Michael! Allways great to be able to stand on the shoulders of guys ('n girls) bigger than me!
[/edit]; added thanks to orignal post and added bias-question 😉
My response is totally biased in favor or SQL Server vs Open Source solutions. "Free" isn't always "Free".. Basically my script is my ETL process to the data to a place where it is in a usable form. The nature of the task was to deliver to a manager a list of customers with the disaster recovery sku in place. I am providing my manger access to the table where this data lands. Didn't really see the need to get SSRS involved. He just wanted a way to track this info as we roll out upgrades to this app.
Hi Michael,
There was no bias in your article; seeing the additional info I'm quite surprised that there wasn't any 🙂
Agree with your observation on "Free":
Free is not Free as in Free beer!
It is Free as in Freedom... that too is not without cost...
Hey; I'm biased too! I try not to be.... but that doesn't always work out!
I (perhaps mis-)understood that you only had to get a teensy detail from "foreign" database-systems ASSUMING that it was chosen through a rigorous selection process to best fit the job. From your later comment I understood that was less so.
To often I suspect that lack of (a broad) skill-set is the reason to spread FUD
Beware!
Sorry for any misunderstandings I'm responsible for! Hope I've been able to clarify!
[/edit]: added on-topic (Free) response
March 20, 2017 at 9:36 am
fschreuder - Monday, March 20, 2017 9:29 AMthedspaincrew - Monday, March 20, 2017 9:07 AMfschreuder - Monday, March 20, 2017 4:51 AMJeff Moden - Sunday, March 19, 2017 4:52 PMGood bit of research there. Thanks for sharing.
Of bigger concern to me is the whole nature of this task. If LINUX and MongoDB is so good (according to some), why is it the folks using those couldn't come up with the report(s) on the LINUX/MongoDB side of the house? Seems like that would have been the better/faster choice instead of dragging data from one server to another.
Why is it you don't have your reportingservice running on your (production)databaseserver? 🙂 Mind you; you respons reads a little biased?
With SSRS in place/activly used; that would be the logical choice for a single datapoint (as I understood from the original post).
Ad-hoc implementations often grow sour on you. That is "multiplatform"!Regards!
Thanks for posting the script Michael! Allways great to be able to stand on the shoulders of guys ('n girls) bigger than me!
[/edit]; added thanks to orignal post and added bias-question 😉
My response is totally biased in favor or SQL Server vs Open Source solutions. "Free" isn't always "Free".. Basically my script is my ETL process to the data to a place where it is in a usable form. The nature of the task was to deliver to a manager a list of customers with the disaster recovery sku in place. I am providing my manger access to the table where this data lands. Didn't really see the need to get SSRS involved. He just wanted a way to track this info as we roll out upgrades to this app.
Hi Michael,
There was no bias in your article; seeing the additional info I'm quite surprised that there wasn't any 🙂
Hey; I'm biased too! I try not to be.... but that doesn't always work out!
I (perhaps mis-)understood that you only had to get a teensy detail from "foreign" database-systems ASSUMING that it was chosen through a rigorous selection process to best fit the job. From your later comment I understood that was less so.To often I suspect that lack of (a broad) skillset is the reason to spread FUD
Beware!Sry for any misunderstandings I'm responsible for! Hope I've been able to clarify!
No worries. Its all good. Hope you find the script useful.
Michael.
March 20, 2017 at 9:38 am
I do! Thank you! 🙂
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply