Viewing 15 posts - 151 through 165 (of 177 total)
Of course this is a problem in procedural programing, not batch programing. Thus, this is the kind of code that makes DBAs (like me) tense up and make ugly...
December 15, 2003 at 11:05 am
There is no way to impersonate or elevate permissions within a stored procedure. Obviously, that's done for security.
I'm not sure what you mean by needing ambiguous access. Are...
December 15, 2003 at 10:44 am
MSDE security works much like SQL Server security. You can never turn off Windows integrated security; you can only turn off SQL Authentication.
However, you should be able to remove...
December 15, 2003 at 10:37 am
Does your new server have exactly the same name as your new server? If so, you should be OK. If not, check @@servername. It's probably coming up...
December 15, 2003 at 10:26 am
Can you post the query, or at least parts of it to give us an idea of what it is doing?
December 15, 2003 at 9:56 am
That's correct, you can't use sp_executesql inside a UDF. Why do you need a function? You could wrape this code inside a stored procedure.
December 15, 2003 at 9:18 am
I'm not sure I'm understanding you correctly, but if I am.... There's no script involved. You would simply issue the statement:
DBCC CHECKDB [database name] REPAIR_ALLOW_DATA_LOSS
After you do,...
December 14, 2003 at 3:59 pm
use sp_executesql with an output parameter, like this:
declare @SQL nvarchar(4000)
declare @params nvarchar(4000)
declare @name varchar(255)
select @SQL = 'Select @name = name from sysobjects where id = 1'
December 14, 2003 at 10:08 am
One option would be to use a trigger to prevent adding more duplicate entries. You could use an instead of trigger to check for existing values utilizing a non-unique...
December 13, 2003 at 10:50 pm
One option would be to use a trigger to prevent adding more duplicate entries. You could use an instead of trigger to check for existing values utilizing a non-unique...
December 13, 2003 at 10:49 pm
You should be able to check the value of @@error from your stored procedure right after the insert or update statement
December 12, 2003 at 2:25 pm
For years, I resisted installing anti-virus software on SQL Servers. And honestly, I've never had a SQL Server infected. However, I have recently changed my thinking.
I do now...
December 12, 2003 at 1:17 pm
I do something similar with a Windows Script that I wrote. You can execute the Windows Script (or Batch file if you prefer) as an additional step in your...
December 12, 2003 at 11:57 am
There is code posted at another site that is supposed to return this information. I haven't tested it myself.
http://www.planet-source-code.com/vb/scripts/ShowCode.asp?txtCodeId=768&lngWId=5
December 12, 2003 at 11:53 am
Have you tried
RESTORE LOG [database name] WITH RECOVERY
December 12, 2003 at 11:46 am
Viewing 15 posts - 151 through 165 (of 177 total)