Comments
Sort by recent activity
Nice one James! That has helped me out as well as I did find using profiler without setting a filter a touch more annoying as all the events were from SSC.
It would be nice to make this "easier" to configure from within the GUI though as I'm sure many others would want to fine tune/disable polling. / comments
Nice one James! That has helped me out as well as I did find using profiler without setting a filter a touch more annoying as all the events were from SSC.
It would be nice to make this "easier" to...
My experience with SSC is that it is fantastic at helping to source control the schema, but as of yet, not so good with the data. I have found that if you want to source control some data from a table, then unless there are a relatively few number of records then SSC suffers from performance issues. And when I say a "few records" a few means in the 100's absolute maximum.
It is one thing to get the data sync'd into an empty database, but when trying to detect changes before a commit to source control, a significant amount of data does cause SSC to spend a lot of time working out the data differences.
It got so bad for us with our platform that we decided to take out data from source control until a future time that SSC can handle data much more effectively. We run the data in as a post build script manual task and I hear on the grapevine that the next version of SSC may have support for these type of pre/post build scripts which would be great!...
Sorry to not to be able to offer a solution. Just wanted to share our experiences and would be keen to find out if there are workarounds to speed up the data sync process in SSC. / comments
My experience with SSC is that it is fantastic at helping to source control the schema, but as of yet, not so good with the data. I have found that if you want to source control some data from a ta...
I believe that this exit error is raised when everything is identical, but it can be suppressed by using the /include:identical setting / comments
I believe that this exit error is raised when everything is identical, but it can be suppressed by using the /include:identical setting
I don't think it is configurable. You break the searches down by type i.e. filter by tables, then by views etc. What are you trying to achieve as there may be another way to achieve what you need to do? / comments
I don't think it is configurable. You break the searches down by type i.e. filter by tables, then by views etc. What are you trying to achieve as there may be another way to achieve what you need t...
Ok, as a workaround and unless anyone can update this thread with a way to configure SQL Search, I would probably look to querying the information schema views if you are unable to refine the search any further. For example:
To find any routines that contain the search term in the name of the routine or definition of the routine you could perform a query similar to:
SELECT * FROM INFORMATION_SCHEMA.ROUTINES
WHERE ROUTINE_NAME LIKE '%something%' OR ROUTINE_DEFINITION LIKE '%something%'
And to find columns containing a term in the column name:
SELECT * FROM INFORMATION_SCHEMA.COLUMNS WHERE COLUMN_NAME LIKE '%something%'
and again for tables containing a term in the name:
SELECT * FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_NAME LIKE '%something%'
There are a number of other information schema views that you can query to search for terms in views, parameters, constraints etc.
I know that it doesn't highlight exactly where the search term is like SQL Search, this may help you achieve in part with what you need to do by compiling a list of objects that contain the search term that you are interested in investigating further. / comments
Ok, as a workaround and unless anyone can update this thread with a way to configure SQL Search, I would probably look to querying the information schema views if you are unable to refine the searc...
Hi Thanks for you reply.
To be honest, I don't believe that the default should be to disable triggers. I have a scenario where triggers have been overused and totally misused by previous database developers and I am unable to reverse this development at this point in time. As such, for me, it isn't really the software doing something wrong, it is myself requiring the software to be more flexible because of bad design decisions made in the past.
If anything, it would be absolutely great to see SQL source control provide the same options that would normally be provided natively through SQL Compare/Data Compare. The dropping/recreating of foreign keys with check/nocheck is another example "option" that should be configurable through SSC.
I feel that having a little "Options" UI within SSC which then got passed through to compare/data compare during the sync process from source control would make the SSC solution hugely more flexible and configurable for us database developers that are haunted by past misdemeanours..
I would appreciate your thoughts? / comments
Hi Thanks for you reply.
To be honest, I don't believe that the default should be to disable triggers. I have a scenario where triggers have been overused and totally misused by previous database d...
Hi Nolan, I too have similar scenarios but the data that i work with is health related.
There is a great book called Protecting SQL Server Data by John Magnabosco/RedGate which gives looks of good information regarding securing/obfuscating data. I've got a printed copy, but i believe you can get an pdf version.
You should be able to adapt some of the examples in the book to obfuscate the cc number and then wire that logic into SQL data generator, probably using the "SQL statement" generator. / comments
Hi Nolan, I too have similar scenarios but the data that i work with is health related.
There is a great book called Protecting SQL Server Data by John Magnabosco/RedGate which gives looks of good ...
I've just tried doing this using version 5.1.6.35 and when inside a literal string, keywords are not being converted to upper case.
e.g. i typed this out all in lowercase and let sql prompt do the formatting without any tweaks from me.
SELECT * FROM sys.tables WHERE name = 'on when'
I don't recall changing anything in particular within the options.
Hope this helps in some way. / comments
I've just tried doing this using version 5.1.6.35 and when inside a literal string, keywords are not being converted to upper case.
e.g. i typed this out all in lowercase and let sql prompt do the ...
Hi snkscore, is it possible to test the compare script against a test instance that mimics your production environment or other similar sandpit type environment?
There are some sql statements that you cannot wrap up within a transaction e.g. full text indexing so i believe that it wouldn't be possible to rollback those type of changes that easily. / comments
Hi snkscore, is it possible to test the compare script against a test instance that mimics your production environment or other similar sandpit type environment?
There are some sql statements that ...
Hi Traci, I was intrigued by your post this morning, so I quickly created this to see if I could achieve what you was after using tsql...
SELECT object_name(object_id) AS 'Tablename', name AS 'ColumnName',
(
SELECT DISTINCT object_name(object_id) FROM sys.sql_dependencies
WHERE class IN (0, 1) AND referenced_minor_id > 0 AND referenced_major_id = C.object_id
FOR XML PATH('Object'), ROOT('Dependencies'), TYPE
) AS 'DependencyXML'
FROM sys.columns C
WHERE EXISTS
(
SELECT 1 FROM sys.sql_dependencies
WHERE class IN (0, 1) AND referenced_minor_id > 0 AND referenced_major_id = C.object_id
)
I'm sure this could be refined and written better, but I hope this may help as a starter... / comments
Hi Traci, I was intrigued by your post this morning, so I quickly created this to see if I could achieve what you was after using tsql...
SELECT object_name(object_id) AS 'Tablename', name AS 'Colu...