User profile for freddy12345

petey wrote: freddy12345 wrote: since i did not tell it to Replace, why is it doing anything, and what is it doing? On SQL Server 2000, REPLACE is not required in order to overwrite an existing database. On SQL Server 2005 and newer, REPLACE is not required if: - you are running the database using the simple recovery model - the database is running using full/bulk-logged recovery model, and there are no entries in the transaction log that needs to be backed up --Thank you for your response. From at least one point of view, it would seem dangerous to allow DB replacement without specific user directive. perhaps from another point of view it is desirable. Yikes. wonder if anyone else has got burned by this? Fortunately, there was very little damage done in this instance. / comments

petey wrote: freddy12345 wrote: since i did not tell it to Replace, why is it doing anything, and what is it doing? On SQL Server 2000, REPLACE is not required in order to overwrite an existi...

0 votes

Thanks for your response, Helen, yes i see the Outcome column and sorting by that is helpful. Still, it is not nearly as helpful as the prior feature, whereby all failed jobs, for all servers, were visible in one window, including the error messages. in one glance, i could see the whole story. creating a report 'by hand' with manually entered dates, is the least helpful of the 3, because i like to check for job errors several times a day. Your company makes great software. i respectfully suggest that usability testing (or, more of it), would be very productive with your software. i used to work at Human Factors International, the world leader in usability, and you might consider their input -- www.humanfactors.com thanks for listening! Fred / comments

Thanks for your response, Helen, yes i see the Outcome column and sorting by that is helpful. Still, it is not nearly as helpful as the prior feature, whereby all failed jobs, for all servers, were...

0 votes

Thank you! This looks like it'll do the trick. Fred / comments

Thank you! This looks like it'll do the trick. Fred

0 votes

Hi Jonathan, Thanks for your response. The person who is actually doing this explains further: "The problem is that the script doesnâ€™t drop all constraints first, so running the script gives errors." does this clarify? Fred / comments

Hi Jonathan, Thanks for your response. The person who is actually doing this explains further: "The problem is that the script doesnâ€™t drop all constraints first, so running the script gives err...

0 votes

Jonathan, sorry, i forgot to include the other info you requested. sql compare 5, ver 5.3.0.44 sql server 2005, sp1 my boss asked me to duplicate this on my own, and follow thru with you. so, i'll be getting back to you on this! thanks so much, Fred / comments

Jonathan, sorry, i forgot to include the other info you requested. sql compare 5, ver 5.3.0.44 sql server 2005, sp1 my boss asked me to duplicate this on my own, and follow thru with you. so, i'll ...

0 votes

Hi David, Thanks for your responses. 1) We made a decision to avoid Print statements for performance reasons so the lack of consistency with SQL Compare is an intentional one. --> it's not clear to me how a print statement would degrade performance. the visibility of how far it's gone is to me far more important than a couple more seconds of execution time. as pointed out in point 3, we're not getting any output messages. 2) To avoid the possibility of being left in an inconsistent state, we will back out completely if a problem arises. --> the sql compare product has some if checks at the edn, and gives a message as to what happened (kind of, that message could be clearer.) when i look at the data compare synch script, it has a begin tran at the start, and a commit tran at the end. if there is a problem with an intervening insert statement--what does it do? keep going, or stop? in either event, i don't see how you do a back out if a problem arises. how do you trap for a problem? 3) This is either a bug, or the target database has changed since the script was generated. If you can provide us with an example of where/how this fails, it would be most useful. --> i could send you my synch script, if that would help. even if the target DB has changed, i'd think you'd want a more graceful way to indicate this, than no messages at all. 4) You're right, we've had this feedback before! We acknolwdge that it's definitely not ideal. The project saves itself automatically but only after a successful 'compare'. This is the same with SQL Compare. --> i'd love to see a 'hotfix' that puts a Save button on the form. you already have the cancel and run buttons, i imagine it should be fairly easy to give us a save. Thanks for considering this. 5) Crashes should not happen. If you can provide us with a way of reproducing this at our end, we'll look into it. --> i am able to cause a crash pretty easily -- in the where clause, just enter it incorrectly. e.g. instead of pk in (1,2,4,5), leave out the 'pk'. if that doesn't do it for you, let me know and i can supply more info. 6) In many situations it is possible to synch views, which will synch the underlying tables, so they are supposed to be listed. However, if both the views and associated tables are selected for synchronization, the synch will fail, so currently you will have to unselect the views. Maybe a better solution would be to have views deselected by default? Let use know your thoughts. --> yes, i think views should be deselected by default. ideally, maybe you could provide user with notice of redundant selections, or even disallow them. might be more complex, but certainly useful. maybe views could be visibly represented in a different way? (separate section). thanks for listening, Fred / comments

Hi David, Thanks for your responses. 1) We made a decision to avoid Print statements for performance reasons so the lack of consistency with SQL Compare is an intentional one. --> it's not clear to...

0 votes

Hi, this won't help the discussion directly, but i just wanted to add that i have created a where clause that references another table, and it seems to work fine, to limt rows considered the way we want. here is my where clause (contactsinfo is the table in focus, and rep table is a separate, related table): contactpk in (select ContactInfoFK from rep r where r.contactinfofk=contactinfo.ContactPK) Fred mohaaron wrote: I'm actually talking about having an additional custom comparison key. So when the comparison key does match then the custom comparison key is used. This way even when the comparison key does match only the matches with a differing custom key will be checked. The comparison key you are talking about is only used for find matches, or what will become update statements, and not to find changed rows. / comments

Hi, this won't help the discussion directly, but i just wanted to add that i have created a where clause that references another table, and it seems to work fine, to limt rows considered the way we...

0 votes

Hi, I am a new user of Sql Backup, andhave the same problem as the poster. I need to stuff a variable list of DB names into the backup command. You have not explained why this: EXEC master..sqlbackup '-SQL " BACKUP DATABASE Staging_116 TO DISK='''+@iBackUpLocation+''' WITH INIT " ' ...does not work, even though it looks correct. and the solution below is more complex. any way to make it work? Thanks, Fred petey wrote: Try this: DECLARE @iDatabaseName varchar(12) DECLARE @iBackUpLocation varchar(260) DECLARE @vBackupName varchar(128) DECLARE @command nvarchar(1024) SET @idatabaseName = 'pubs' SET @iBackUpLocation = 'c:\temp\pubs.sqb' SET @vBackupName = 'Backup pubs' SET @command = '-SQL "BACKUP DATABASE [' + @iDataBaseName + '] TO DISK=''' + @iBackUpLocation+''' WITH INIT, NAME=''' + @vBackupName+'''"' EXEC master..sqlbackup @command / comments

Hi, I am a new user of Sql Backup, andhave the same problem as the poster. I need to stuff a variable list of DB names into the backup command. You have not explained why this:EXEC master..sqlba...

0 votes

How can we help you today?

freddy12345

Comments