Timeline for Creating many random test database entries
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 29, 2017 at 19:31 | answer | added | janos | timeline score: 0 | |
| Aug 3, 2015 at 21:14 | history | edited | msanford | CC BY-SA 3.0 |
edited body
|
| Aug 2, 2015 at 21:28 | history | edited | Jamal | CC BY-SA 3.0 |
deleted 187 characters in body; edited tags; edited title
|
| Aug 9, 2012 at 13:13 | vote | accept | msanford | ||
| Aug 8, 2012 at 18:59 | comment | added | Andrey Agibalov | Accessing database million times is always bad idea. If you need to have a million of entries, just make this SP generate you all these entries at once and then call it once. | |
| Aug 8, 2012 at 18:56 | comment | added | msanford | @loki2302 I've never run long queries like this before, so basically: is running this type of stored procedure a million times a bad idea, is there a more efficient way to do it, or anything else that jumps out? | |
| Aug 8, 2012 at 18:51 | answer | added | Andrey Agibalov | timeline score: 2 | |
| Aug 8, 2012 at 18:43 | comment | added | Andrey Agibalov | So, what's about your original question? Is this approach any faster? :-) | |
| Aug 8, 2012 at 18:38 | history | edited | msanford | CC BY-SA 3.0 |
Added stored procedure
|
| Aug 7, 2012 at 17:12 | comment | added | Andrey Agibalov | Stored procedures? net.tutsplus.com/tutorials/an-introduction-to-stored-procedures | |
| Aug 7, 2012 at 17:11 | history | tweeted | twitter.com/#!/StackCodeReview/status/232886726652227584 | ||
| Aug 7, 2012 at 16:41 | history | asked | msanford | CC BY-SA 3.0 |