Viewing 15 posts - 11,686 through 11,700 (of 14,953 total)
"She who must be obeyed"... there's a Jack Lemmon movie on that kind of subject. It's called, "How to Murder Your Wife". Pretty funny, actually (and nobody gets...
January 9, 2009 at 11:33 am
I'm with Matt on this one. Implicit inserts (no list of column names) are easy, but they cause more problems in the long run than they're worth.
I've seen situations...
January 9, 2009 at 11:30 am
Sounds like the e-mail process hasn't finished with it before the delete process fires up. You may need to make that asynchronous, and have a status-check step before the...
January 9, 2009 at 9:49 am
SQL can have a password expiration rule in it. Check the properties of the server, on the Security tab. Also check the properties of the login at the...
January 9, 2009 at 9:48 am
Duplicate post. Reply added to other copy.
January 9, 2009 at 9:32 am
Are you talking about an SQL Server account password, or a Windows domain password, or something else?
January 9, 2009 at 9:32 am
Why not just do:
update dbo.Table01
set SomeField = SomeValue
where Whatever = Something
update dbo.Table02
...
update dbo.Table03
...
....
Why "loop through", instead of just writing the code?
January 9, 2009 at 9:30 am
The other solution would be to insert the desired rows into temp tables and then Union the temp tables.
January 9, 2009 at 9:28 am
foxjazz (1/8/2009)
the plan would be to use it as the key in an insert statement.
You're going to be better off letting SQL handle the identity value of new inserts, and...
January 9, 2009 at 9:13 am
I live in Tampa, and it's pleasant here today. Visited Spokane, WA, last month (family up there) and it was -4F when I got there (that's -20C for everyone...
January 9, 2009 at 9:01 am
Nice, useful article. Good scripts. Thanks.
January 9, 2009 at 8:47 am
They should almost always be set to "on". I can't think of a specific reason to have them off, but it might be required for some obscure problem.
January 8, 2009 at 3:29 pm
The only way to completely avoid possible issues with this is to start with a datetime variable set to 0, then use dateadd year, dateadd month and dateadd day to...
January 8, 2009 at 3:27 pm
Your best bet for a 100% accurate answer is call Microsoft and ask them. Only takes a few minutes, and the answer is guaranteed.
January 8, 2009 at 3:21 pm
For one thing, don't even think about upgrading that server to SQL 2008. So far as I know, that won't do 7.
I'd be inclined to check the service contract...
January 8, 2009 at 3:19 pm
Viewing 15 posts - 11,686 through 11,700 (of 14,953 total)