Viewing 15 posts - 7,201 through 7,215 (of 7,472 total)
using cmdshell it will work if you have the authority.
exec xp_cmdshell 'date ....'
January 21, 2004 at 12:27 am
did the hyperlinks bring any light in the darkness ?
Search the KB, there were more articles where you can find "bpool" ..
January 21, 2004 at 12:12 am
First things we do is add the windows SQLserver-administrators-group as login and add it to the sysadmins serverrole.
Then we always remove builtin\administrators from the sqlserver-logins !
Our SQLservers all run using a windows...
January 20, 2004 at 1:12 am
Keep in mind you can only start jobs you own !
To avoid overauthorising users so they can start jobs, I use an alert which starts the job, so they only raise...
January 20, 2004 at 12:59 am
Windows version ?
SQLServer version ?
AWE enabled ?
(check
- http://support.microsoft.com/default.aspx?scid=kb;en-us;319477&Product=sql2k
- http://support.microsoft.com/default.aspx?scid=kb;en-us;323212&Product=sql2k
January 20, 2004 at 12:09 am
Jonathan
SQL7 -> no cascading deletes through DRI. That must be done using triggers.
Dan,
The DRI-checking will be done by sqlserver, so provide FK-indexes to support it.
If those indexes hurt performance to...
January 19, 2004 at 7:26 am
My guess,
you have a table with nullable columns that you use with a unique index.
A primary key constraint cannot be defined on nullable columns.
With a unique index, you can...
January 19, 2004 at 4:57 am
should be single quotes ..
SELECT @TestSql = 'INSERT INTO @TestTable SELECT au_id,au_fname From [pubs].[dbo].[authors] '
EXECUTE (@TestSql)
January 19, 2004 at 2:31 am
Is this what you're looking for ?
select J.Name as JobName, RP.program_name
from msdb..sysjobs J with (nolock)
inner join master..sysprocesses RP with (nolock)
on RP.program_name like 'SQLAgent - TSQL JobStep (Job '...
January 16, 2004 at 8:33 am
I hope your day today will be mutch better
Regarding the hyperlink : Believe me, once you seen Sheryl explain the whole stuff, you'll...
January 15, 2004 at 2:30 am
No, this only means that a litle testing is advisable for anyone who wants to build some knowlage of an rdbms. It's not because any solution works "optimal" for me,...
January 15, 2004 at 12:04 am
I thought the smilies would give enough indication that that reply was only ment to be a litle dry humor. After all there was no sql-technical info involved
January 14, 2004 at 11:52 pm
As always, you'll have to compare execution plans and runtimes to build your choice on. Hey, this may even by the occasion for a 'aha-erlebnis'
January 14, 2004 at 6:20 am
Hey, I thought the were bits and pieces of bricks and cement with your last reply
As far as I'm concerned you may as well...
January 14, 2004 at 4:48 am
Perform it on both, maybe that gets it all into the daylight, but at least perform it where you are having the problem (i.e. the select).
- QA\Query\display estimated execution plan...
January 13, 2004 at 7:04 am
Viewing 15 posts - 7,201 through 7,215 (of 7,472 total)