Comments
Sort by recent activity
hi, I experienced the same behavior.
upgraded sql search from v2.x to 3.x (also within SSMS14)
rebooted
sql search displayed no results no matter what search I attempted (a very different behavior than in the past - I've used this for many years).
I uninstalled sql search
I upgraded sql prompt from 9.0 ish to 9.5.23
I reinstalled sql search 3.2.1
Sql search now returns results
One thing I noticed, when upgrading from sql search 2, the installer placed sql search 3 content into the sql search 2 path. When I reinstalled sql search 3 from scratch, it placed its content into the sql search 3 path. I'm not sure if this is the/part of the issue or not. Sorry I did not keep better track of version numbers.
/ comments
hi, I experienced the same behavior.
upgraded sql search from v2.x to 3.x (also within SSMS14)
rebooted
sql search displayed no results no matter what search I attempted (a very different beha...
Hi, this is a pretty old thread, but I ran into the same issue for specific extended properties that were not excluded by the standard extended prop. ignore option. To ignore extended properties sp_addextendedproperty N'sys_sensitivity_label_name' - I found the option by editing the project and checking "Ignore sensitivity classifications". Hope this works for you, though I doubt it's still an issue this far out! / comments
Hi, this is a pretty old thread, but I ran into the same issue for specific extended properties that were not excluded by the standard extended prop. ignore option. To ignore extended properties s...
I'll email you a screen shot... / comments
I'll email you a screen shot...
oops, I just found it, but you have to right-click in the differences area to get the option. Glad it's still there. / comments
oops, I just found it, but you have to right-click in the differences area to get the option. Glad it's still there.
Correct, I was just posting a reply to Michelle's question. / comments
Correct, I was just posting a reply to Michelle's question.
* The most common mapping error we get, because of source control, are duplicate files.
"A duplicate definition for the table dbo.TableName has been found while processing the script database. . . . " / comments
* The most common mapping error we get, because of source control, are duplicate files.
"A duplicate definition for the table dbo.TableName has been found while processing the script database. . ....
I'll see if I can get an example of the triggers - and make sure that's really what I saw happening as I was in a hurry [image] / comments
I'll see if I can get an example of the triggers - and make sure that's really what I saw happening as I was in a hurry
And the resulting deploy script does this:
PRINT N'Altering permissions on [dbo].[GetWebinarEmailsAsFetchXmlValues]'
GO
GRANT EXEC ON [dbo].[GetWebinarEmailsAsFetchXmlValues] TO [xxxx]
GO
REVOKE EXECUTE ON [dbo].[GetWebinarEmailsAsFetchXmlValues] TO [xxxx]
which actually revokes the permission it just gave resulting in a real difference and creates a never ending loop of differences if you continue to run the deploy scripts one after the other. / comments
And the resulting deploy script does this:
PRINT N'Altering permissions on [dbo].[GetWebinarEmailsAsFetchXmlValues]'
GO
GRANT EXEC ON [dbo].[GetWebinarEmailsAsFetchXmlValues] TO [xxxx]
GO
REVOKE ...
(removed) / comments
(removed)
Yes, we are also thinking of using this method to store object definitions in source control. We'd like to use sql compare to compare our source control scripts to what's on a given server, however, sql compare marks the objects as different because what it gets from the server has CREATE and what it gets from source control says ALTER. That is the only difference. Is there an option to ignore these differences? / comments
Yes, we are also thinking of using this method to store object definitions in source control. We'd like to use sql compare to compare our source control scripts to what's on a given server, howeve...