Viewing 15 posts - 5,851 through 5,865 (of 6,105 total)
You've declared @sql as a varchar, not nvarchar:
quote:
DECLARE @sql VARCHAR(1000)
Then later on you try and...
January 22, 2002 at 7:10 am
I tried to execute the extended stored procedure in Query Analyzer and it gave the error saying xp_userlock requires parameter @subcommand and so on. Once I had put in...
January 21, 2002 at 4:08 pm
Hrm. That eliminates all the "slap yourself on the forehead" type of issues. You're able to connect to the other SQL Server properly right now?
K. Brian Kelley
January 21, 2002 at 1:14 pm
It sounds like you are connecting with a SQL Server login? Did you check if the SQL Server setup is for NT authentication only or both NT and SQL...
January 21, 2002 at 12:59 pm
Starting with the basics and making sure the network guys didn't do something, are you able to ping the server from where you are trying to add it? If...
January 21, 2002 at 12:52 pm
What we did in a DR environment was take our server backup and restored everything but the data files (we operate in a 24/7 environment which means there isn't a...
January 21, 2002 at 10:57 am
The problem with the leading % is that SQL Server is unable to use an index since the first part of the string could be anything. As a result,...
January 21, 2002 at 10:51 am
All I've been able to determine thus far is that it has three mandatory parameters:
@subcommand
@resource
@dbid
K. Brian Kelley
January 18, 2002 at 6:13 pm
It does sound like a permissions problem.
He can execute the following statement in Query Analyzer to verify the account he's using is indeed a sysadmin:
EXEC sp_helpsrvrolemember 'sysadmin'
Permissions...
January 18, 2002 at 5:59 pm
You also have the option of executing using the WITH COMPILE if you're executing the stored procedure manually. Here's the excerpt from Books Online:
January 18, 2002 at 11:33 am
Right, but the original insert caused the second insert to fire because of the trigger. So SQL Server is going to return the identity from the trigger insert. ...
January 18, 2002 at 9:30 am
@@Identity doesn't work this way. @@Identity is tied to a particular statement. It's not tied to a database.
For instance, if I do a
INSERT MyTable
(Column1, Column2)
VALUES
('For Column1', 'For...
January 18, 2002 at 8:21 am
The sp_spaceused system stored procedure should work. If you want hit all the user tables, you can use the sp_MSForEachTable stored procedure like so:
EXEC sp_msForEachTable @Command1 =...
January 17, 2002 at 3:23 pm
DBCC FREEPROCCACHE clears out the procedure cache, that is correct. If you do a before and after on the syscacheobjects table in the master database you'll see the effect.
DBCC...
January 17, 2002 at 2:39 pm
It may. I know if you issue literal, you can enter a site command, for instance site stats. Beyond that, I can't really speak of.
K. Brian Kelley
January 16, 2002 at 4:01 pm
Viewing 15 posts - 5,851 through 5,865 (of 6,105 total)