Comments
Sort by recent activity
hi Frangooch,
try this guide. However, you can enable it pressing the intellisense button into SSMS [image] / comments
hi Frangooch,
try this guide. However, you can enable it pressing the intellisense button into SSMS
hi @nirms,
data compare will generate the diff script (and will execute it if you wish) without any schema change. / comments
hi @nirms,
data compare will generate the diff script (and will execute it if you wish) without any schema change.
Got it, typical problem, isn't it? I can understand you :-)
Actually, it's really simple to "rewrite" them all. You could script only the stored procedures in one file, then, replace the full qualified name with the synonym. For creating the synonyms, you can extract with a regexp the fully qualified names and generate the CREATE SYNONYM script.
If you figure out how to match the strings, it will be simple, don't you think? / comments
Got it, typical problem, isn't it? I can understand you :-)
Actually, it's really simple to "rewrite" them all. You could script only the stored procedures in one file, then, replace the full quali...
Hi @MrBaas,
my reply is related to a certain SQL Server object. I've been in the same trouble years ago, and now the solution is still working. Would you try to use SYNONYMS instead a fully qualified name when calling "external" databases? The compilation of the stored procedures should use the deferred name resolution.
Hope I've got it correctly.
Let us know :-) / comments
Hi @MrBaas,
my reply is related to a certain SQL Server object. I've been in the same trouble years ago, and now the solution is still working. Would you try to use SYNONYMS instead a fully qualifi...
SQL Compare is an helper for deployment. It generates diff scripts, it doesn't mark the "version" of the release and it doesn't allows you to link the changesets. Since you're using TFS, you could comment a changeset in order to know if it's ready for deployment, but if you want to know the information release by release, you should use a combination of a build server and a release management tool.
Take a look here, DLM Automation. You can use also the Release Management tool in TFS. / comments
SQL Compare is an helper for deployment. It generates diff scripts, it doesn't mark the "version" of the release and it doesn't allows you to link the changesets. Since you're using TFS, you could ...
Hi SKIT,
if you're not using any tool for deployment, SQL Source Control is not related to this task. You can understand the version and the drift using DLM Dashboard. / comments
Hi SKIT,
if you're not using any tool for deployment, SQL Source Control is not related to this task. You can understand the version and the drift using DLM Dashboard.
Hi @RitaR,
SQL Compare does the ddl comparison (CREATE TABLE, PROCEDURE, FUNCTION, and so on). This means that the generated script involves only the structures, not data. If you want to compare data, you've to use SQL Data Compare.
That said, you're speaking bout "static data" which is the term used by SQL Source Control for "linked" records. This tool allows you to store into your version control also the INSERT of the data of tables, but it is separated from the comparison tools concepts. They should be used both for comparing structures and data, but they don't depend on how your SQL Source Control is set.
If your goal is to "deploy" the artifacts created by SQL Source Control, you've to use DLM Automation tool or to create a nuget package (that could be used in deployment tools) / comments
Hi @RitaR,
SQL Compare does the ddl comparison (CREATE TABLE, PROCEDURE, FUNCTION, and so on). This means that the generated script involves only the structures, not data. If you want to compare da...
Hi,
Could you please tell us how did you link the database with SQL Source control? Did you link it using the "Link database to Source Control" option? If so, and you're receiving errors, I think that it should work following these steps:
1. create database using the script (not checkin in into the SQL Source Control folder)
2. linking using the "Link to Source Control" (to git) using Sql Server Management Studio
after these two options, everything should work.
I'm a little bit confused about the Databases\OnlineBanking\_Initialization\ folder, which should not be part of the working base folder.
In this link, there's how SQL Source Control works behind the scenes.
Sorry if I didn't get it. / comments
Hi,
Could you please tell us how did you link the database with SQL Source control? Did you link it using the "Link database to Source Control" option? If so, and you're receiving errors, I think t...
Hi @Elizabeth_Close_M1st,
can you try to send the error details? If you get a view with an error string, you get also a hyperlink with the error description. / comments
Hi @Elizabeth_Close_M1st,
can you try to send the error details? If you get a view with an error string, you get also a hyperlink with the error description.
Hi @Pat,
are you speaking about SQL Source Control and git versioning? When you save the objects, you will see in uncommitted status using git/team explorer. Are you thinking about a tab into SSMS before sending objects to git? You've already the Push/Pull button right now.
Did I get it? / comments
Hi @Pat,
are you speaking about SQL Source Control and git versioning? When you save the objects, you will see in uncommitted status using git/team explorer. Are you thinking about a tab into SSMS ...