User profile for isme

PeterG wrote: pressing return gives me a fresh prompt or I can just type my command in again Thanks for checking that. I didn't think about pressing return! PeterG wrote: Could you try pressing return to see if this fixes it, please let me know either way. I no longer have access to the RedGate demo VM I was testing on. If I can set up my own test environment I will try your workaround and let you know. / comments

PeterG wrote: pressing return gives me a fresh prompt or I can just type my command in again Thanks for checking that. I didn't think about pressing return! PeterG wrote: Could you try pressi...

0 votes

We resolved the issue this morning. There were two issues here. One was my mistake; the other looks like a gap in the documentation. 1. The SQL Server service account did not have a login on the server. For SQL Backup to use the account, it has to be sysadmin on the server. I added the service account DEV\sqlservice as a sysadmin on the server. The server did actually log the failed logins, but I was looking in the agent log rather than the server log. D'oh! The UI installer over RDP gave the clearest indication of this issue. It would be helpful if the error messages were more consistent. 2. The command line installer requires a password for the service account. For SQL Backup to use the service account, it needs to know the password. In the end, a command like this worked for me: psexec \\$TargetServer G:\media\SQBServerSetup.exe /VERYSILENT /SUPPRESSMSGBOXES /SVCUSER $svcuser /SVCPW $svcpw It produced a result like this: PsExec v1.98 - Execute processes remotely Copyright (C) 2001-2010 Mark Russinovich Sysinternals - www.sysinternals.com Connecting to REMOTESERVER...Starting PsExec service on REMOTESERVER...Connecting with PsExec service on REMOTESERVER...Starting G:\media\SQBServerSetup.exe on REMOTESERVER... G:\media\SQBServerSetup.exe exited on REMOTESERVER with error code 0. The SQL Backup UI now shows a yellow "Trial" icon next to the server. Success! The command line installer does not force you to provide a password, and the documentation suggests that one is unnecessary to use the server's account. I imagine this would work if the server is running under one the default Windows accounts, but we use dedicated service accounts with passwords. It would be helpful if the documentation was clearer on this point. As a security note, I don't recommend using my solution for a production deployment. psexec does not encrypt its connection to the remote server. Don't allow someone to sniff your production password over the network! / comments

We resolved the issue this morning. There were two issues here. One was my mistake; the other looks like a gap in the documentation.1. The SQL Server service account did not have a login on the ser...

0 votes

I can't install it using the GUI tools either. Any ideas what the root cause could be? 5. Using the UI over RDP I double click to run the installer. I accept all the default settings and supply the correct password for the account that SQL Server runs as. When I click Next at 'Select SQL Server authenticaion mode', I see an error message. Failed to verify that the account (DEV\sqlservice) is a member of the SQL Server sysadmin fixed server role for the selected instance. SQL error: Login failed for user 'DEV\sqlservice'. This installation may not be able to install the SQL Backup extended stored procedures. User another login. The SQL Server error log shows no failed login attempts. 6. Using SQL Backup UI on my workstation I run SQL Backup on my workstatation. I open the "Add SQL Server" dialog, supply the server name and the correct password for the SQL Server service account, and accept the defaults. I click finish, SQL Compare validates the options, then the installation starts. It fails at the first step "Copying and running SQBServerSetup". REMOTESERVER: Server Component Installation - Failed ====================================================== Copying and running SQBServerSetup - Failed ------------------------------------------- Error running installer: exit code 6200 The SQL Backup Agent service failed to connect to the SQL Server instance using the SQL login provided. Exit code 6200 means "SQL authenticated user name or password is invalid." Again, the SQL Server error log shows no failed login attempts. / comments

I can't install it using the GUI tools either. Any ideas what the root cause could be?5. Using the UI over RDP I double click to run the installer. I accept all the default settings and supply the ...

0 votes

Thanks, Aaron. I've created a UserVoice item to add an option to ignore tabs over a certain number of connections. Vote here: http://redgate.uservoice.com/forums/944 ... oring-tabs / comments

Thanks, Aaron. I've created a UserVoice item to add an option to ignore tabs over a certain number of connections. Vote here:http://redgate.uservoice.com/forums/944 ... oring-tabs

0 votes

We use SQL Compare and TortoiseSVN together because we find they work better for us that SQL Source Control. SSC gave us lots of confusing and difficult-to-reproduce SVN errors that just didn't happen when we used TortoiseSVN. We'd be grateful if you could submit a suggestion to deal with the RedGate.ssc files in SQL Compare, either by ignoring them altogether or by creating them when writing a script folder. Thanks for your help! / comments

We use SQL Compare and TortoiseSVN together because we find they work better for us that SQL Source Control. SSC gave us lots of confusing and difficult-to-reproduce SVN errors that just didn't hap...

0 votes

I wasn't aware that SQL Compare actually used SQL Source Control in the background. Thanks for explaining that. The read behavior is consistent. Both SQL Source Control and SQL Compare fail to read a repo without a RedGate.ssc file. The write behavior is not the same. SQL Compare can't write directly to an SVN repo. When you set SVN as the target and go to the deployment wizard, your only option is to create a deployment script. Would be great if the tools were more consistent. Would it be possible to ignore the presence of RedGate.ssc? If not, would it be possible for SQL Compare to write a RedGate.ssc file whenever it creates a set of scripts? / comments

I wasn't aware that SQL Compare actually used SQL Source Control in the background. Thanks for explaining that. The read behavior is consistent. Both SQL Source Control and SQL Compare fail to read...

0 votes

It not absolutely clear what the correct behavior should be. Should SQL Compare create an empty file called RedGate.ssc, like SQL Source Control does? Or should SQL Compare just stop checking for RedGate.ssc altogether? I would prefer the second option because it seems simpler from a user's point of view. / comments

It not absolutely clear what the correct behavior should be. Should SQL Compare create an empty file called RedGate.ssc, like SQL Source Control does? Or should SQL Compare just stop checking for R...

0 votes

Thanks for logging those, Evan. SC-3645 is the most important one here. Somehow our workflow ends up producing hundreds of empty files paired with script files with 1 on the end every few months. When we gather enough someone shouts about it and we decide to clean up. We've learned to be more vigilant about our commits in any case. It would be great if SQL Compare was more tidy in the first place :-) / comments

Thanks for logging those, Evan. SC-3645 is the most important one here. Somehow our workflow ends up producing hundreds of empty files paired with script files with 1 on the end every few months. W...

0 votes

Hi Evan, Thanks for looking into it. Were you able to reproduce the issues? Can you report on the internal status? Thanks, Iain / comments

Hi Evan, Thanks for looking into it. Were you able to reproduce the issues? Can you report on the internal status? Thanks, Iain

0 votes

In October Brian Donahue quoted a developer's explanation for bug 1. If we delete a file, then the source control will just think that the file is missing, and will not delete it from source control when the changes are checked in. Good version control tools can deal with missing files. It's a common scenario. hg has the --addremove option which automatically removes missing files. TortoiseSVN automatically deletes missing files that are checked for commit. I think SQL Compare should not worry about what version control thinks. When it's in script-writing mode, it should just concentrate on writing a tidy set of scripts. / comments

In October Brian Donahue quoted a developer's explanation for bug 1. If we delete a file, then the source control will just think that the file is missing, and will not delete it from source contr...

0 votes

How can we help you today?

isme

Comments