Viewing 15 posts - 8,386 through 8,400 (of 13,469 total)
adding traces is the way to go.
the default trace captures DDL statements, but rolls nover fairly quickly.
you can add your own trace to capture all DML statements, or filter them...
November 23, 2010 at 8:27 pm
Phil Brammer (11/23/2010)
November 23, 2010 at 11:02 am
ok, i compared my snippets to your code, and the only thing i have that is different is that my code always gets the value of the context_info from a...
November 23, 2010 at 10:57 am
a whole lot of knee jerk reactions about "but it's not supported!", but since it works on SQL 2008 ( and someone reported it works all the way thru...
November 23, 2010 at 10:37 am
S_Kumar_S (11/22/2010)
November 22, 2010 at 10:18 pm
This situation can be tough. replication and log shipping assume some degree of access to theSQL Server itself. It sounds like you do not have access to that.
Is this shared...
November 22, 2010 at 1:21 pm
in general, it depends how many rows at a time you are deleting.
SQL server will automatically create row-level locks for single row deletions, so there would not be contention with...
November 22, 2010 at 12:29 pm
you can put an expression, just like you were planning, in the query, and it will appear as results int he query.
here's your specific example: note i simply added the...
November 22, 2010 at 9:29 am
there is a forum post on here somewhere where someone compared explicitly dropping a temp table created inside a proc, vs letting the system destroy it automatically when the...
November 22, 2010 at 9:19 am
BenWard (11/22/2010)
Thanks lowell.These aren't input parameters but rather individual variables created like DECLARE @fYetAnotherDamnedNumber AS FLOAT
I'm going crosseyed looking at so many variables!
ok, ASFAIK, ither than memory/disk constraints, there's no...
November 22, 2010 at 8:48 am
from my old notes, SQL2000 had these limits. 2005/2008 might be more now.
·UDF can have upto 1023 input parameters, Stored Procedure can have upto 2100 input parameters.
November 22, 2010 at 8:04 am
as long as the other instances are also SQL2008 R2, then yes.
the backup is stored in a specific format to teh SQL version; it's not specific to the instance type...
November 22, 2010 at 7:48 am
also a valid file name cannot have colons in it('D:\backup\AdventureWorks_22 Nov 2010 19:29:35:003.BAK'), so you need to make sure the string you are building is valid for a filename.
i usually...
November 22, 2010 at 7:17 am
if you take a proc, stick it in the master database, and mark it as a system object, then it will use the datasase reference of the calling SQL.(it also...
November 22, 2010 at 6:10 am
I believe the target schema is 2008; it worked just fine for me...the object id of my table was actually exactly the same as the article.
in 2005 Express, i get...
November 22, 2010 at 5:51 am
Viewing 15 posts - 8,386 through 8,400 (of 13,469 total)