Viewing 15 posts - 11,326 through 11,340 (of 13,460 total)
among the same versions (ie 8.* to any other v8 or 9.* to any other v9) all backups are compatible with the same version..
so if i backup with SQL2005...
Lowell
April 1, 2009 at 7:46 am
duplicate post.
no need to cross post to multiple forums it fractures the answers you get and makes posters duplicate others work.
the "Recent Posts" link shows us everything.
continue the thread here:
http://www.sqlservercentral.com/Forums/Topic687890-357-1.aspx
Lowell
April 1, 2009 at 7:41 am
duplicate post.
no need to cross post to multiple forums it fractures the answers you get and makes posters duplicate others work.
the "Recent Posts" link shows us everything.
continue the thread here:
http://www.sqlservercentral.com/Forums/Topic687890-357-1.aspx
Lowell
April 1, 2009 at 7:41 am
i'm still reading your code, but it looks like it is doing nothing more than getting a bunch of links for navigation recursively right?
i'd like to see the code of...
Lowell
April 1, 2009 at 7:31 am
both != and <> are "not equal" and are valid operators for SQL server...i used != because the web site sometimes interprets that as html and makes it disappear.
Lowell
April 1, 2009 at 6:46 am
did you accidentally run the script on the master database instead of a specific database? or a different database than the one you needed to?
Lowell
April 1, 2009 at 6:40 am
to do it the hardway, you have to check @@error after each update/insert: each command changes the @@error:
ALTER procedure MyProc
As
BEGIN
begin transaction
update1
if @@error != 0 GOTO Bailout
update2
if @@error != 0...
Lowell
April 1, 2009 at 6:34 am
it depends on the scope;
outside of a stored procedure, if you issue that command, it is for the life of the session/window or until you set XACT_ABORT to OFF;
if you...
Lowell
April 1, 2009 at 6:19 am
it really depends...the devil is in the details.
why are you breaking up related data into two separate servers? This looks like a red flag to me; are you archiving the...
Lowell
April 1, 2009 at 6:15 am
use a transaction like his:
SET XACT_ABORT ON --any error, rollback any trnasactions
BEGIN TRAN
--do first update
--second update
....
--last update
COMMIT TRAN --if there was any error, everything rollsback, no error checking needed
Lowell
April 1, 2009 at 5:09 am
duplicate post.
no need to cross post to multiple forums it fractures the answers you get and makes posters duplicate others work.
the "Recent Posts" link shows us everything.
continue the thread...
Lowell
April 1, 2009 at 5:06 am
syntax wise, your query is fine; you didn't say what the issue is you need help explaining.
can you tell us what is wrong? does the query fail? do you need...
Lowell
April 1, 2009 at 5:01 am
In order to "Use" a server, a connection has to already be established...SSMS does not have any commands that you can use in TSQL to change or modify your connection...so...
Lowell
April 1, 2009 at 4:58 am
yeah when your nose is lost in the details,things like that still ding me once in a while, even after I've worked around it a zillion times.
Lowell
March 31, 2009 at 3:48 pm
if you use NOT IN, you must exclude the NULLs; anything IN = or LIKE NULL is undefined:
SELECT * FROM BIG_THINGS
WHERE THING_ID NOT IN
(SELECT THING_ID FROM THINGS WHERE THING_ID...
Lowell
March 31, 2009 at 3:33 pm
Viewing 15 posts - 11,326 through 11,340 (of 13,460 total)