Viewing 15 posts - 25,261 through 25,275 (of 59,102 total)
Greg Edwards-268690 (11/30/2013)
Gary Varga (11/29/2013)
Jeff Moden (11/29/2013)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2013 at 7:03 pm
dwain.c (12/1/2013)
Where in the world did you come up with such a thing?
Heh... after spending hours on posts like this one wondering why the hell the code won't short circuit...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2013 at 6:39 pm
sqlsurfing (12/1/2013)
Jeff Moden (11/30/2013)
Set it to "single user" then immediately to "multi-user" and then immediately execute the restore command. Of course, these 3 things should be in a script.
Good...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2013 at 6:26 pm
EamonSQL (12/1/2013)
because a downstream process then takes the xml which feeds into a report.I can't amend the downstream process.
Oh my. I feel for you there.
Did Magoo's answer...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2013 at 6:20 pm
sqlfriends (12/1/2013)
Recently the server has an automatically restart at a night and a weekend.
In the HP Proliant...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2013 at 6:04 pm
I don't use SSIS but, speaking from an old dude's perspective, I'd likely make the loading of each table a separate package for reusability and then have a control package...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2013 at 5:59 pm
I don't have an answer right now but I have a friend that works with servers that half a half TByte and more. I know he's running some form...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2013 at 5:54 pm
Shifting gears again, VARCHAR(50) for eMail addresses simply isn't wide enough. I'd make that a VARCHAR(250) and still be prepared for the occasional truncation. Yes, I've seen it...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2013 at 5:45 pm
pietlinden (12/1/2013)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2013 at 5:35 pm
I would first ask the Developers how they knew they rolled everything back and how they knew they didn't drop something that they didn't add.
The other thing might be that...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2013 at 5:17 pm
ChrisM@Work (11/26/2013)
Jeff Moden (11/25/2013)
rlortega (11/25/2013)
So what minimum T-SQL skills are necessary if you're a DBA, not a developer?
To be honest... learning to read minds and to anticipate "what's coming" by...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2013 at 5:13 pm
Are you able to correctly answer and carry on a fairly decent conversation about those "direct" questions? If not, you might not survive the interview.
Shifting gears back to your...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2013 at 5:00 pm
I'd also like to recommend that you avoid 3 part naming in code. Create a synonym for the table in the other database and then stick to 2 part...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2013 at 3:55 pm
Duplicate post. To keep from splitting up answers, please don't post replies here. Please see the same post at the following URL. Thanks.
http://www.sqlservercentral.com/Forums/Topic1518687-2799-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2013 at 3:52 pm
dwain.c (9/24/2013)
Create Table #SensorHistory
(
...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2013 at 3:21 pm
Viewing 15 posts - 25,261 through 25,275 (of 59,102 total)