Red Gate forums

RE: Found new bug when using "Add object existence check" option

JohnnyT — Mon, 20 May 2013 20:33:55 GMT

Brian Donahue wrote:

Hello,

Thanks for supplying all of the output from SQL Compare... would it be possible to script a scenario that caused this problem to happen? I can see where the problem occurs in your deployment but I can't figure out how to reproduce it so I can submit a proper bug report.

I'll see what I can do. It may take some time for me to set this up.

RE: Command line automation does not sync extended properties

james.billings — Mon, 20 May 2013 17:18:49 GMT

Thanks for your post.

Based on an initial test here, DB level extended properties should get scripted OK, so I need to check a few things:

- are these extended properties the ones that SQL Source Control adds, or your own ones?
- are you running the command line with the same credentials as when you tried it through the GUI?
- what version of SQL Compare are you on?
- what *exact* command line are you running? Can you post an example? For instance I was able to script the differences in extended properties with pretty much no options:

Code:

sqlcompare.exe /db1:database1 /db2:database2 /sf:d:\sync.sql

3.4.1.73 no longer finds GIT?

Mindflux — Mon, 20 May 2013 16:46:48 GMT

I just installed the whole SQL Dev toolbelt, and was well on my way to using GIT as my repo..

I did my initial commit and that worked, then I got a message that 3.4.1.73 was available for SQL Source control, since updating it can no longer find GIT when I try and do a commit.. however dropping to a command prompt I still can run git (it's in my path).

Code:

Command:
git commit -F "C:\Users\USERNAME\AppData\Local\Temp\m2wwaakq.xgb.txt" -o "C:\temp\db\\"

Output:
'git' is not recognized as an internal or external command,

operable program or batch file.

Exit code:
1

SQL Backup Agent restarting unexpectedly....

CorrinHarris — Mon, 20 May 2013 16:17:50 GMT

We have 2 clustered instances of SQL that can shares nodes. Normally instance A runs on node 1 and instance B runs on node 2. Both have their own Redgate SQL Backup Agent services set up and running as clustered resouces, SQL Backup Agent-A (on node 1) and SQL Backup Agent-B (on node 2) . However we have noticed that when an instance fails over - both SQL Backup Agents seem to start/restart on the active node - we would have expected just one to start - there are no disk dependencies etc. This also happens when we manually fail back.

The only error we can find is as follows:-
Faulting application SQBCoreService.exe, version 6.5.1.9, time stamp 0x2a425e19, faulting module unknown, version 0.0.0.0, time stamp 0x00000000, exception code 0xc0000005, fault offset 0x000a000d, process id 0x1b30, application start time 0x01ce4ffceedb85c0.

Any assistance would be appreciated...

RE: Fastest Way:Converting MTS to MP4 keeping HD-quality

PaulGoldstraw — Mon, 20 May 2013 16:00:10 GMT

Thanks for the info. Isn't this a SQL Prompt forum though?

RE: Sending Files to source control server failed

james.billings — Mon, 20 May 2013 15:02:15 GMT

Thanks for your posts.

We're still investigating why the policies don't work correctly in some environments- as you suggest, it seems related to certain combinations of versions.

The very latest release (you should find if you go to Help > Check for Updates) allows you to disable the policy enforcement completely so you don't need to enter the #ignorepolicies comment each time. Please see here for instructions on how to set that up.

RE: Profiling a different machine

AdamsGuitar — Mon, 20 May 2013 14:48:36 GMT

I understand. Please consider implementing something like this; I know that other memory profiler products provide simple utilities that can run on client machines to capture memory snapshots that can then be copied to a machine running the full version to perform the analysis. As it is now, I may have to use another profiler to solve this problem, which doesn't make me terribly happy.

How to check database schema version

kulmam92 — Mon, 20 May 2013 14:44:09 GMT

Hi

When using sql source control and svn to manage DB schema, is there a way to check which version of db schema that a database has? I'm asking if there's any version table or version information stored in the database, so that I can check the schema version without using source control tool.

Thank you,
Yong

RE: Change user for TFS

Brian Donahue — Mon, 20 May 2013 14:43:53 GMT

You can run SQL Server Management Studio as a different user, and then SQL Source Control will connect as that user.

RE: can't exclude identical objects?!

howarthcd — Mon, 20 May 2013 14:22:16 GMT

Hi Red-Gate

It's been four months since we initially reported the filter bug (for which you created SC-6165).

Are you able to confirm when this issue will be resolved?

Thanks
Chris