![]() Rather than try and learn it inside out then come across as all knowledgeable, I‘m going to write about the process as I experience it for the first time. Given my previous positive experiences with Red Gate products I thought I’d write this blog a little differently. In the database world that means it has to play nice with SQL Server Management Studio (henceforth known only as SSMS), just as tools like VisualSVN or AnkSVN play nice with Visual Studio. To make database versioning practical it needs to integrate seamlessly into the development process, that is it needs to align to the tools and practices developers use. Sure, there are various mechanisms out there to script objects out into the file system and version those but it’s a real pain to actually synchronise back into other environments. The simplicity with which we version other applications files – HTML, images, classes, etc – hasn’t been readily achievable in the database world. Versioning database objects very much fits into the same realm in that it’s a nightmare to do without a dedicated tool. They’re tools I tend to berate developers for not having and have regularly waxed lyrical about in the past, albeit it within 140 characters until now. After all, SQL Source Control is from the guys who brought us SQL Compare and Data compare, two of my all-time favourite tools in the “stuff that would be a real pain to do without” category. ![]() ![]() I knew it was going to be good before even seeing it. 在SQL Cource Control窗口中单击Help - Serial Number - Enter Serial Number
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |