Activity overview
Latest activity by peter eh
How to ignore different datatyes
We have a system with a live and an archive DB and I now need to track all changes made in the live DB in the archive DB. The problem is that a field named tst has the datatype timestamp in the liv...
Hello Russell, thank you so much for your answer. There are no dump files, no other corresponding entries in SQL or Windows log files, no jobs (except SQL Monitor) that always run at the time in question. On one server the errors stopped suddenly and without any changes, on the other one they appear in the SQL log about 200 times per day. This is really puzzling. I had already read the sqlservercentral article, but unfortunately it doesn't help because no solution is described and he doesn't write if the problem was fixed after the reboot. The recovery interval for all DB's on both servers was set to 60 from the beginning. Next week we will patch and boot both servers, see what it looks like afterwards. / comments
Hello Russell,thank you so much for your answer. There are no dump files, no other corresponding entries in SQL or Windows log files, no jobs (except SQL Monitor) that always run at the time in que...
CImageHelper Failed with SQLMonitor 9.1.6
For all our SQL instances controlled with SQL Monitor we get the following error message in the SQL Server Log:CImageHelper::Init () Failed load of symbol file with path = C:\Instance\MSSQL14.xxxx\...
How to remove old license admin
As a license admin I can manage our redgate user lincenses - that works as expected. Now I have to remove another license admin who has left the company, but I found no way to do that. I can invite...
I don't think this vote is the same as tbsam and me wanted - " ... an option whereby under each table, there is tick boxes ... - not an exclude on each table, I'm looking for one line like "tabledef: timestamp = binary(8)" and all these differences over lets say 500 tables are excluded. This would be really helpful and would save a lot of time by contrast with todays work. Today I have to click on every single table and deselect or unmap this field from the comparison. Hard and stupid work on big databases with over 500 tables.
Other useful excludes I can think of:
alldef: nvarchar(50) = varchar(50) -> meaning: excludes all differences with this expression in tabledefinitions, views, sp's, functions, ...
tabledef: nvarchar(length) = varchar(length) -> meaning: all table fields with the same name und the same number between the brackets are excluded from the difference viewer as long as there is no other difference. Useful for projects that migrate to unicode.
allname: tbs* = tbl* -> meaning: we are in the process of changing the table prefixes, exclude all differences that relate to these table prefixes.
...
Don't know if this is practicable, but it would be a lifesaver specially when you have thousands of database objects to maintain.
Peter / comments
I don't think this vote is the same as tbsam and me wanted - " ... an option whereby under each table, there is tick boxes ... - not an exclude on each table, I'm looking for one line like "tabled...
Add me to the list that want to see the project browser back.
1) new comparison vs. saved project is about 1:200
2) ~ 100
3) new database or special check conditions e.g. exclude all fields with timestamp on one and binary(8) on the other side (this example would be a great pick for an option in SQL Compare and SQL Data Compare too)
4) 1. database name, 2. server/instance name allways for source and target
5) database name, missing the chance to sort the datasources after database name in v11 and before!
6) database name (once again)
And Jason's comment has my full concurrence: Can I complain about the new icons, too? I have no idea what each is supposed to represent when I look at them on my taskbar. What was easy has now become difficult. It's a pity if something good is made worse.
Peter / comments
Add me to the list that want to see the project browser back.
1) new comparison vs. saved project is about 1:200
2) ~ 100
3) new database or special check conditions e.g. exclude all fields with ti...
I fully agree with Doug here, especially his points 2 and 3.
After working for nearly 12 years with RedGate tools, for me v12 ist the visually worst release ever. If I open v10 and v12 side by side with the same databases and the same differences, I see a clear structure with colored icons that are not flat and grid lines in v10 - striking points my eyes can focus on. On the v12 side I see a blue, grey, black patchwork blurring his content with hardly no point my eyes can focus on, so in v12 for me it's harder to recognize differences and in general much more weary to work with.
To answer Matt's question about contrast issues, if you could make the skin (colors, icons, grid lines) from v10 available as an option in v12 and later releases, then the RedGate tools could bring me back the fun to work with, as it was for many years.
Peter / comments
I fully agree with Doug here, especially his points 2 and 3.
After working for nearly 12 years with RedGate tools, for me v12 ist the visually worst release ever. If I open v10 and v12 side by sid...
Hi Chris
Yes this is the FAQ I've read.
Thanks
Peter / comments
Hi Chris
Yes this is the FAQ I've read.
Thanks
Peter
Hi Chris
- I suppose that we have those deadlocks before I tried SQL Monitor, but we don't see them in the logs.
- The deadlocks still appear now, even after the shutdown of SQL Monitor.
-> something must have changed!
After some research I think I found the reason. SQL Monitor must have enabled Trace Flag 1204, which isn't enabled on our production servers usually.
Can you comfirm this Trace Flag activation?
Thanks for your help
Peter / comments
Hi Chris
- I suppose that we have those deadlocks before I tried SQL Monitor, but we don't see them in the logs.
- The deadlocks still appear now, even after the shutdown of SQL Monitor.
-> somethi...
SQL Monitor 2 and Deadlocks ... ?
I'm seeing some very strange behaviour here ...
After installing, I tested SQL Monitor 2 in our development and test environment. Everything looks fine there. Then I monitored two production server...