Viewing 15 posts - 1,021 through 1,035 (of 1,047 total)
'proof' was probably too strong a word. (The only injection proof server is one with no connections. lol)
July 7, 2009 at 12:07 pm
I've used sp_executesql but not sp_execute. The former provides for safe use of parameter specifiers for building injection-proof dynamic SQL. Maybe the latter is an application specific...
July 7, 2009 at 10:35 am
There is no way to find this out from SQL Server. SQL profiler can record this stuff but it has to have been running at the time.
July 6, 2009 at 12:34 pm
How wide are the rows? (I suppose I should have specifically asked that as well).
I would try to keep the table as one (logical) table if at all possible. You...
June 30, 2009 at 10:53 am
That's a very good question... one I'd be asking the architect of that design.
June 30, 2009 at 10:33 am
It is really only dangerous in the case where appropriate and strict adherence to minimum required permissions and complex password safeguards are lacking or non-existent. Unfortunately this is true in...
June 22, 2009 at 2:27 pm
look at the profile you set up for this account... see if you have checked the box: "this server requires a secure sockets connection" (or something like that).
Your server may...
June 2, 2009 at 11:23 am
I've always built my own log shipping mechanisms and they are easier to manage and more robust since they have more intelligence and robustness into the design than the stock...
May 15, 2009 at 2:27 pm
if there were just a relative few you just fix them manually. If not, a cursor working on a set of these duplicates would allow you to consolidate the data...
April 24, 2009 at 12:25 pm
you need to simply delete the ones you don't want. Write a procedure to resolve duplicates. Next you need to modify the business logic of your application and/or the...
April 24, 2009 at 11:49 am
I just kill any processes in that happen to be in the database before I execute the restore.
cursor loop through sys.sysprocesses where dbid = {yourdbid} and execute a dynamic kill...
April 24, 2009 at 8:03 am
SMO is pretty much required if you need to generate scripts of database objects or perform certain other server operations programaticaly.
April 20, 2009 at 9:11 am
GilaMonster (4/13/2009)
There's a lot more to consider than performance.Truncate requires ALTER TABLE permissions, delete requires DELETE permissions
This is called CONTROL permission, and yes the truncate will fail without it.
Truncate will...
April 14, 2009 at 11:01 am
I always use this:
select rowcnt from sys.sysobjects O JOIN sys.sysindexes I on O.id = I.id and indid = 1 where type = 'U' and name = 'TABLENAME'
April 6, 2009 at 11:53 am
Viewing 15 posts - 1,021 through 1,035 (of 1,047 total)