December 5, 2014 at 5:08 am
We only have the command line version of Red Gate Data Compare and I'm trying to compare our live and failover Reporting Servers. The problem I have is when I try to output the contents of the Contents column on the Catalog table to a .csv file it gets returned as <Binary Data> rather than the actual binary data. Is there anyway of returning the Contents data as either the Binary data from the table or ideally, as XML? I fully expect there to be differences in between the two tables to allow for the different data sources they use but if I can see the XML, I can make sure that's the only difference.
How to post a question to get the most help http://www.sqlservercentral.com/articles/Best+Practices/61537
December 5, 2014 at 7:55 am
You should be able to set a switch that outputs as a report. Here's the documentation showing how that works. You would want /Report.
I didn't know we had a command line only version of the tool.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 5, 2014 at 8:10 am
Grant Fritchey (12/5/2014)
You should be able to set a switch that outputs as a report. Here's the documentation showing how that works. You would want /Report.I didn't know we had a command line only version of the tool.
Thanks Grant. That was my first thought but the /report switch only works with SQL Compare apparently.
The command line only versions come in the Automation Pack. It seems like a pretty good value way of making some of the Red Gate tools available. Of course it appears there are limitations.
How to post a question to get the most help http://www.sqlservercentral.com/articles/Best+Practices/61537
December 5, 2014 at 8:27 am
Oh heck, I thought I was on the Data Compare page. Sorry about that.
Yep, no report on the Data Compare command line. Again, sorry.
So script or script file won't work? Export goes out to a .csv file. Not the same as report, but...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 5, 2014 at 8:40 am
The script file works fine and exporting to a csv works fine for the other columns I tried it on, it just seems not to like the binary data for the report. I've even got it to export xml into a csv. It's formatted like a pig's breakfast but the principal works.
It's a bit annoying that a really useful piece of functionality that's been provided with one of the tools, hasn't with another. But you get what you pay for I suppose.
How to post a question to get the most help http://www.sqlservercentral.com/articles/Best+Practices/61537
December 6, 2014 at 3:40 am
I'd suggest putting in a request for it. It might not be that hard to implement. I'll put in a request from my side too.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply