131 reputation
6
bio website
location Leipzig
age 33
visits member for 3 years, 1 month
seen Mar 6 at 8:13

Swing dancing, Fantasy books crunching (specificaly Song of Ice&Fire), DSA playing freak.

.NET Integration Test Coder (MSTest, Nunit, heavy datadriven) at day for work, and interested in everything new in .NET and the web right now (Reactive Extensions, SignalR, MVC3/FubuMvc, Html5, CSS3). Right now learning Javascript and frameworks (e.g. knockoutJs), the list never ends.

Also got a nag for UX and design, want to see the whole picture bottom -> up. Working on a website right now.


Sep
24
awarded  Autobiographer
Jan
20
awarded  Commentator
Jan
20
comment Sql Server: how to validate schema against a textual representation (XML or the like) natively?
"Dude", that's beside the point. Agreed, scripting would be hard on that base. I don't need it, never wrote I did. I need something that warns via merge collision that migration script are incompatible between branches. Which is reasonable, it removes potential errors before testing. Sorry that I sounded aggressive to you. I remained calm while comments containing "?!!?" jumped at me. Which were quickly edited away. That was the "vibe" in the beginning, never saw that anywhere else on SE. So much for "not so different". Therefor my last comment.
Jan
16
comment Sql Server: how to validate schema against a textual representation (XML or the like) natively?
wo worlds collide here: the world of DBAs who have no control at all about their toolchain are pretty much Microsoft/Redgate driven, and the world of "newage" C# devs where "we just create the tools we need, noSql is good, all power to the dev". DBAs don't care about dev process, hate ORMs (for good reason) and care just about Ops. DBAs also don't work with 3-way difftools, constant merging, Mercurial/Git, CI servers, etc.. Different needs, different opinions. One of these old culture clashes I guess. Not too much empathy for each other. Sad, but that's just how the current situation is
Jan
16
comment Sql Server: how to validate schema against a textual representation (XML or the like) natively?
"there is no click - click - finish and export to xml" - why do you assume I search for one? I was in search for a script exporting to XML/similar (title was misleading, fixed that). Similar to sp_help. The metadata is "in there", I just need a script, perf is not important, it's done on builtime as a validation step on the CI system. All I'm looking for is a script that dumps all relevant infos, I can translate that myself, I've done such things a lot in the past. If Redgate had something like that I would be happy to use that, but afaik they only export to SQL scripts. Guess its SMO again..
Jan
16
revised Sql Server: how to validate schema against a textual representation (XML or the like) natively?
added 294 characters in body
Jan
16
comment Sql Server: how to validate schema against a textual representation (XML or the like) natively?
They use SMO, I have actually written the same for migration in pure C# without a GUI. This time I was hoping to save some dev time. I was just assuming that there's gotta be people here knowing this stuff which wouldn't kneejerk-downvote a simple reaosnable question. Edit: something along the lines of sp_help for all the tables.. why was noone mentioning that? Just found it..
Jan
16
revised Sql Server: how to validate schema against a textual representation (XML or the like) natively?
added 789 characters in body; edited title
Jan
16
comment Sql Server: how to validate schema against a textual representation (XML or the like) natively?
it's not about migration or scripting, it's about schema validation on a textual (XML or whatever) format
Jan
16
comment Sql Server: how to validate schema against a textual representation (XML or the like) natively?
I don't get why that was downvorted.. it is a perfectly legitimate usecase.. wanting to diff two schemas with a textual difftool used in development. There are even tools for this, see schemacrawler.sourceforge.net ; I have hard times to believe there's nothing native built in
Jan
16
comment Sql Server: how to validate schema against a textual representation (XML or the like) natively?
it does matter.. with migrations, there are already a bunch of solutions, plenty actually.. all pretty much genrating SQL scripts, as Sql server scripting does.. but I'm looking at a different strategy for different reasons, so I need a textual representation of Sql server.. I don't have the time to argue why I need it, let's just assume it is for good reasons
Jan
16
awarded  Editor
Jan
16
revised Sql Server: how to validate schema against a textual representation (XML or the like) natively?
added 209 characters in body; edited title
Jan
16
comment Sql Server: how to validate schema against a textual representation (XML or the like) natively?
I should have been clearer: I mean I need a script, but no SQL up/down migration script.. will update the title..
Jan
16
comment Sql Server: how to validate schema against a textual representation (XML or the like) natively?
A colleague showed me, he had a SQL statement, unfortunately I can't find it anymore.. used it, worked
Jan
16
asked Sql Server: how to validate schema against a textual representation (XML or the like) natively?
Apr
30
awarded  Popular Question
Oct
12
awarded  Scholar
Oct
12
accepted Does the compatibility level for sql server work reliably for scripts?
Oct
12
comment Does the compatibility level for sql server work reliably for scripts?
@Martin Smith the point is, that migrating a sql server 2008 R2 instance with around 10 databases with fulltext catalogs for 20 devs is a bit of work. We don't have a centralized DB script testing for Sql2005, and someone decided that it is better to prohibit such scripts than let them be found by testing.