Timeline for Inline edit SQL Server database rows from Visual Studio
Current License: CC BY-SA 3.0
31 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 16, 2017 at 13:50 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Aug 14, 2017 at 16:30 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jul 14, 2017 at 16:48 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jun 6, 2017 at 16:27 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| May 3, 2017 at 15:42 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Mar 19, 2017 at 17:10 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Feb 17, 2017 at 13:00 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jan 15, 2017 at 9:06 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Dec 13, 2016 at 5:27 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Nov 9, 2016 at 8:20 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Oct 5, 2016 at 11:59 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Aug 29, 2016 at 14:04 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jul 27, 2016 at 18:45 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jun 9, 2016 at 9:28 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| May 10, 2016 at 2:40 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Nov 28, 2014 at 19:13 | review | Close votes | |||
| Dec 1, 2014 at 18:50 | |||||
| Jul 24, 2013 at 15:21 | comment | added | Paul | Aaron, in what world is someone pointing VS at a production DB. Clearly this is a development\test environment where this kind of approach is suitable and appropriate. | |
| Jul 23, 2013 at 21:23 | history | edited | QFDev | CC BY-SA 3.0 |
added 409 characters in body
|
| Jul 23, 2013 at 18:59 | comment | added | QFDev | It's more a case of getting stuff done, furthermore it's documented and supported in SSMS msdn.microsoft.com/en-us/library/5x6z1x9d.aspx. | |
| Jul 23, 2013 at 17:36 | history | tweeted | twitter.com/#!/StackDBAs/status/359728853377232896 | ||
| Jul 23, 2013 at 16:58 | comment | added | Aaron Bertrand | Good and bad habits all start somewhere. | |
| Jul 23, 2013 at 15:40 | comment | added | QFDev | For a two man team working on a beta web application (where data corrections are common place), this is overkill. I appreciate that this level of discipline would be required for large high traffic databases but it doesn't work for me. This functionality was always there in Visual Studio (and still is for 2008 instances). | |
| Jul 23, 2013 at 15:30 | answer | added | Kin Shah | timeline score: 1 | |
| Jul 23, 2013 at 15:27 | comment | added | Aaron Bertrand |
If you started a transaction before firing off at the hip, consequences are ultimately NULL because you can issue a ROLLBACK. You can't undo points and clicks.
|
|
| Jul 23, 2013 at 15:20 | comment | added | QFDev | Mistakes can be made using either of these methods but the consequences may well be far more serious if a clause is left off a DML statement. Even with the locks on the table, with a narrow SELECT statement I can't see the advantage of manually creating all these different UPDATE clauses? Then again I'm not a DBA. | |
| Jul 23, 2013 at 15:14 | comment | added | Aaron Bertrand |
That's why you say BEGIN TRANSACTION; and don't run COMMIT TRANSACTION; until you're sure. Are you saying you're more likely to fat-finger an UPDATE statement that you can review before executing, than to click in the wrong cell or update a row to the wrong value as you're hopping around a spreadsheet happy to be going quickly?
|
|
| Jul 23, 2013 at 15:13 | comment | added | QFDev | But what about the risk of leaving a clause off an UPDATE statement and inadvertently corrupting a ton of data? | |
| Jul 23, 2013 at 15:11 | comment | added | Aaron Bertrand | Quicker <> better. For one, if you make a mistake, will you notice? Also how do you tell someone else what you did, store the data change in source control, etc. etc.? And do you have any idea what kind of locks open table takes on the underlying system? If this is production you could be asking for trouble. Just because I can wash the dishes with a power washer doesn't mean I should. | |
| Jul 23, 2013 at 15:09 | comment | added | QFDev | Why wouldn't I? It's quicker for a start. If I have a bunch of updates to make across multiple rows on different columns, surely it's easier to run one query, place the cursor in the various boxes and over-type the data? As opposed to writing multiple UPDATE statements? | |
| Jul 23, 2013 at 14:58 | history | edited | QFDev |
edited tags
|
|
| Jul 23, 2013 at 14:50 | history | asked | QFDev | CC BY-SA 3.0 |