November 4, 2013 at 3:35 pm
Fal (11/4/2013)
jasona.work (11/4/2013)
The joy and fun of migrating DBs to a new server...Trying to get in touch with the people who need to update the application, people potentially trying to stall to make other people look bad, people who never get back with you...
The backup->copy->restore->check users->update backup software process...
What fun...;-)
We can swap war stories. I'm currently engaged moving all our servers "into the cloud".
Forgive my if I sound a little air-headed and make insubstantial comments. :hehe:
Fal.
Been there, done that -- I feel your pain. (And the lack of appreciation how much effort it takes, from the managers who read marketing blurbs about "effortless migration.")
November 4, 2013 at 4:00 pm
Revenant (11/4/2013)
Greg Edwards-268690 (11/4/2013)
Revenant (11/4/2013)
Jack Corbett (11/4/2013)
Enjoying trying to work with rs.exe to automate some report deployment issues. Especially enjoying the fact that the .rds XML format used when creating data sources in VS/BIDS/SSDTBI 2008 is not compatible with the format used by ReportingServices2010.CreateCatalogItem.Visual Studio converts them. OTOH, it may force you to fork the project in TFS, if you are using it.
I just love how 2012 uses VS 2010 for lack of BIDS in 2012. 😀
Seems like a bait and switch of sorts.
I wonder what they did in 2014......
You now have 2013, and MSFT promised to keep up with the SQL Server development -- it is now the Servers and Tools division.
If you feel like kicking some asses over there, please let me know.
2014 CPT2, have you loaded it yet?
I like some of the direction in the BI space for features, it just seems they have some disconnects.
For a project type wizard to just more or less disappear, and SSDT goes back to 2010, was just like it was an afterthought. It confused more than a couple developers I'm sure.
November 4, 2013 at 4:22 pm
Greg Edwards-268690 (11/4/2013)
Revenant (11/4/2013)
Greg Edwards-268690 (11/4/2013)
Revenant (11/4/2013)
Jack Corbett (11/4/2013)
Enjoying trying to work with rs.exe to automate some report deployment issues. Especially enjoying the fact that the .rds XML format used when creating data sources in VS/BIDS/SSDTBI 2008 is not compatible with the format used by ReportingServices2010.CreateCatalogItem.Visual Studio converts them. OTOH, it may force you to fork the project in TFS, if you are using it.
I just love how 2012 uses VS 2010 for lack of BIDS in 2012. 😀
Seems like a bait and switch of sorts.
I wonder what they did in 2014......
You now have 2013, and MSFT promised to keep up with the SQL Server development -- it is now the Servers and Tools division.
If you feel like kicking some asses over there, please let me know.
2014 CPT2, have you loaded it yet?
I like some of the direction in the BI space for features, it just seems they have some disconnects.
For a project type wizard to just more or less disappear, and SSDT goes back to 2010, was just like it was an afterthought. It confused more than a couple developers I'm sure.
Could you/would you word it as a QA item? Please... thanks.
November 4, 2013 at 6:17 pm
Fal (11/4/2013)
jasona.work (11/4/2013)
The joy and fun of migrating DBs to a new server...Trying to get in touch with the people who need to update the application, people potentially trying to stall to make other people look bad, people who never get back with you...
The backup->copy->restore->check users->update backup software process...
What fun...;-)
We can swap war stories. I'm currently engaged moving all our servers "into the cloud".
Forgive my if I sound a little air-headed and make insubstantial comments. :hehe:
Fal.
When I hear managers talking about the cloud idyllically I usually respond "You know what happens to clouds when it rains, right?"
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
November 5, 2013 at 1:08 am
SQLRNNR (11/4/2013)
Ed Wagner (11/4/2013)
SQLRNNR (11/4/2013)
jasona.work (11/4/2013)
The joy and fun of migrating DBs to a new server...Trying to get in touch with the people who need to update the application, people potentially trying to stall to make other people look bad, people who never get back with you...
The backup->copy->restore->check users->update backup software process...
What fun...;-)
I always enjoy the biz stall tactics
I know what you mean. I also love the ever-popular "When I said it should do this, I meant it should do that" syndrome when they didn't think things through to begin with. Fun times...
Fundamental DBA skill - telepathy
... and, high velocity pork-chop launchers. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
November 5, 2013 at 6:37 am
Fal (11/4/2013)
jasona.work (11/4/2013)
The joy and fun of migrating DBs to a new server...Trying to get in touch with the people who need to update the application, people potentially trying to stall to make other people look bad, people who never get back with you...
The backup->copy->restore->check users->update backup software process...
What fun...;-)
We can swap war stories. I'm currently engaged moving all our servers "into the cloud".
Forgive my if I sound a little air-headed and make insubstantial comments. :hehe:
Fal.
Image in my head of someone tossing servers out the window...
---------------------------------------------------------
How best to post your question[/url]
How to post performance problems[/url]
Tally Table:What it is and how it replaces a loop[/url]
"stewsterl 80804 (10/16/2009)I guess when you stop and try to understand the solution provided you not only learn, but save yourself some headaches when you need to make any slight changes."
November 5, 2013 at 6:46 am
jcrawf02 (11/5/2013)
Fal (11/4/2013)
jasona.work (11/4/2013)
The joy and fun of migrating DBs to a new server...Trying to get in touch with the people who need to update the application, people potentially trying to stall to make other people look bad, people who never get back with you...
The backup->copy->restore->check users->update backup software process...
What fun...;-)
We can swap war stories. I'm currently engaged moving all our servers "into the cloud".
Forgive my if I sound a little air-headed and make insubstantial comments. :hehe:
Fal.
Image in my head of someone tossing servers out the window...
Hopefully with large helium balloons attached to them, to take them up to "the cloud." :hehe:
I know I'm going to need to migrate these DBs again in the future, either when we go to Windows Server 2012, or SQL 2012. I'm thinking about dealing with the security requirements (You want a network share? Why? Justify it! No, you need a special dispensation for a service account to have access to it!) and next time setting up log shipping between the old and new servers. Then when the app-owner is ready to pull the trigger, take one last log backup, offline the DB, restore the log backup and recover on the new server and my part is (mostly) done.
On an unrelated note, only about 56 days until I get to go to the NHL Winter Classic!
:w00t::w00t::w00t:
November 5, 2013 at 7:42 am
Revenant (11/4/2013)
Jack Corbett (11/4/2013)
Enjoying trying to work with rs.exe to automate some report deployment issues. Especially enjoying the fact that the .rds XML format used when creating data sources in VS/BIDS/SSDTBI 2008 is not compatible with the format used by ReportingServices2010.CreateCatalogItem.Visual Studio converts them. OTOH, it may force you to fork the project in TFS, if you are using it.
Yup, we are using TFS. It is just a bit frustrating when it is hard to find documentation on it and, in reality, all they needed to do in ReportingServices2010 was support one more XML format. Especially when you consider that they most likely knew that VS/BIDS/SSDTBI didn't support the new format.
I'm ending up writing some VB that parses the rds, creates a DataSourceDefinition, and uses CreateDataSource. I assume that must be what the Deploy process in VS/BIDS/SSDTBI does.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
November 5, 2013 at 7:47 am
Greg Edwards-268690 (11/4/2013)
Revenant (11/4/2013)
Jack Corbett (11/4/2013)
Enjoying trying to work with rs.exe to automate some report deployment issues. Especially enjoying the fact that the .rds XML format used when creating data sources in VS/BIDS/SSDTBI 2008 is not compatible with the format used by ReportingServices2010.CreateCatalogItem.Visual Studio converts them. OTOH, it may force you to fork the project in TFS, if you are using it.
I just love how 2012 uses VS 2010 for lack of BIDS in 2012. 😀
Seems like a bait and switch of sorts.
I wonder what they did in 2014......
I actually understand that they haven't been totally in sync with versions of VS to do SSRS and SSIS.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
November 5, 2013 at 8:50 am
Jack Corbett (11/5/2013)
Greg Edwards-268690 (11/4/2013)
Revenant (11/4/2013)
Jack Corbett (11/4/2013)
Enjoying trying to work with rs.exe to automate some report deployment issues. Especially enjoying the fact that the .rds XML format used when creating data sources in VS/BIDS/SSDTBI 2008 is not compatible with the format used by ReportingServices2010.CreateCatalogItem.Visual Studio converts them. OTOH, it may force you to fork the project in TFS, if you are using it.
I just love how 2012 uses VS 2010 for lack of BIDS in 2012. 😀
Seems like a bait and switch of sorts.
I wonder what they did in 2014......
I actually understand that they haven't been totally in sync with versions of VS to do SSRS and SSIS.
This makes upgrades more difficult than they should be. You spend time going under the covers to figure out what is messed up, then have to make a decision. Create your own hack, or do some rebuilding.
And if we can create a hack, you'd think someone at Microsoft would see the issue and create / publish more information. And maybe some recommendations / tools for mixed environments.
I can understand progress, and not being totally backwards compatible. But as more of these products have become more dependent on each other, it is harder for many shops to upgrade everything at once. For the whole BI stack, you start to include SharePoint and Office, so it becomes pretty broad in an Enterprise. So when you start talking desktops, you've gotten to a whole different level.
November 5, 2013 at 3:47 pm
jasona.work (11/5/2013)
jcrawf02 (11/5/2013)
Fal (11/4/2013)
jasona.work (11/4/2013)
The joy and fun of migrating DBs to a new server...Trying to get in touch with the people who need to update the application, people potentially trying to stall to make other people look bad, people who never get back with you...
The backup->copy->restore->check users->update backup software process...
What fun...;-)
We can swap war stories. I'm currently engaged moving all our servers "into the cloud".
Forgive my if I sound a little air-headed and make insubstantial comments. :hehe:
Fal.
Image in my head of someone tossing servers out the window...
Hopefully with large helium balloons attached to them, to take them up to "the cloud." :hehe:
I know I'm going to need to migrate these DBs again in the future, either when we go to Windows Server 2012, or SQL 2012. I'm thinking about dealing with the security requirements (You want a network share? Why? Justify it! No, you need a special dispensation for a service account to have access to it!) and next time setting up log shipping between the old and new servers. Then when the app-owner is ready to pull the trigger, take one last log backup, offline the DB, restore the log backup and recover on the new server and my part is (mostly) done.
On an unrelated note, only about 56 days until I get to go to the NHL Winter Classic!
:w00t::w00t::w00t:
That's the underlying reason for our 'move project'. Our data centre pins us in our office and we can't move to flashier digs until the DC moves. Putting in it the cloud means we wont have that restriction in the future.
And, oh! How marvelous it will be. Wall to wall SQL Server 2012 Enterprise Edition; Master Data Services for handling our myriad datasets; Always On Availability Groups. Need more RAM or CPU? A few clicks and it's done! Running out of disk space? Select a new amount from a dropdown list!! Rainbow coloured unicorns will prance around the office and large bottles of quality red wine will fall from the heavens....
And then Bean Counters in Head Office looked at the cost of SQL Server 2012 Enterprise Edition and said "WTF? It's over 50% of the entire project budget. We can save a motza if we use a managed instance."
And so now I'm stripping enterprise features from all our databases in order to shovel them into a managed instance. To give you an idea, it's a bit like the change in Tutankhamun before and after mummification.
:crying:
Fal.
November 5, 2013 at 5:56 pm
Fal (11/5/2013)
jasona.work (11/5/2013)
jcrawf02 (11/5/2013)
Fal (11/4/2013)
jasona.work (11/4/2013)
The joy and fun of migrating DBs to a new server...Trying to get in touch with the people who need to update the application, people potentially trying to stall to make other people look bad, people who never get back with you...
The backup->copy->restore->check users->update backup software process...
What fun...;-)
We can swap war stories. I'm currently engaged moving all our servers "into the cloud".
Forgive my if I sound a little air-headed and make insubstantial comments. :hehe:
Fal.
Image in my head of someone tossing servers out the window...
Hopefully with large helium balloons attached to them, to take them up to "the cloud." :hehe:
I know I'm going to need to migrate these DBs again in the future, either when we go to Windows Server 2012, or SQL 2012. I'm thinking about dealing with the security requirements (You want a network share? Why? Justify it! No, you need a special dispensation for a service account to have access to it!) and next time setting up log shipping between the old and new servers. Then when the app-owner is ready to pull the trigger, take one last log backup, offline the DB, restore the log backup and recover on the new server and my part is (mostly) done.
On an unrelated note, only about 56 days until I get to go to the NHL Winter Classic!
:w00t::w00t::w00t:
That's the underlying reason for our 'move project'. Our data centre pins us in our office and we can't move to flashier digs until the DC moves. Putting in it the cloud means we wont have that restriction in the future.
And, oh! How marvelous it will be. Wall to wall SQL Server 2012 Enterprise Edition; Master Data Services for handling our myriad datasets; Always On Availability Groups. Need more RAM or CPU? A few clicks and it's done! Running out of disk space? Select a new amount from a dropdown list!! Rainbow coloured unicorns will prance around the office and large bottles of quality red wine will fall from the heavens....
And then Bean Counters in Head Office looked at the cost of SQL Server 2012 Enterprise Edition and said "WTF? It's over 50% of the entire project budget. We can save a motza if we use a managed instance."
And so now I'm stripping enterprise features from all our databases in order to shovel them into a managed instance. To give you an idea, it's a bit like the change in Tutankhamun before and after mummification.
:crying:
Fal.
Talk about a balloon popping....
That core licensing model can take a bit to plan for.
Some of the Enterprise features do save money and reduce risk. So they might pay for it in other ways.
Ironically, when we went to a remote data center, we had the smallest servers running Ent. Edition, but used it for the features. Others were forced to bite the bullet due to the hardware choice for VM's, when they could have easily continued using Std Edition.
One of the most interesting things was how people tried to interpret the licensing model in a virtual environment. Just because you allocate 1 proc in VM, doesn't mean much at the end of the day.
November 5, 2013 at 8:20 pm
Thankfully, I don't see it getting cloudy any time soon in my future. 🙂
November 5, 2013 at 11:11 pm
First of all, thanks to Steve for fixing the SQL formatting issues in my recently published article:
How to Design, Build and Test a Dynamic Search Stored Procedure [/url]
So I'm chatting on Skype with a Security Engineer friend of mine, telling him about the articles that SSC has so graciously published for me and I send him a link to my Guest Columnist page.
Within seconds he tells me the email address I registered to the site and then shortly thereafter I get an email with a link that says "if you want to change your password, press this link."
The @#$@@ is trying to hack my SSC account! Just goes to show what happens when you befriend and ethical hacker!
Hope that link expires so I don't need to change my password.
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St
November 6, 2013 at 5:47 am
dwain.c (11/5/2013)
First of all, thanks to Steve for fixing the SQL formatting issues in my recently published article:How to Design, Build and Test a Dynamic Search Stored Procedure [/url]
So I'm chatting on Skype with a Security Engineer friend of mine, telling him about the articles that SSC has so graciously published for me and I send him a link to my Guest Columnist page.
Within seconds he tells me the email address I registered to the site and then shortly thereafter I get an email with a link that says "if you want to change your password, press this link."
The @#$@@ is trying to hack my SSC account! Just goes to show what happens when you befriend and ethical hacker!
Hope that link expires so I don't need to change my password.
Nice work, Dwain. I hope people see the methodical approach you took to solve the problem and take it to heart.
Viewing 15 posts - 42,061 through 42,075 (of 66,712 total)
You must be logged in to reply to this topic. Login to reply