Viewing 15 posts - 121 through 135 (of 2,386 total)
It seems the data for your query/sp was not in memory when you noticed it runs longer. In order to confirm it, try to free the data buffer using DBCC...
April 27, 2005 at 8:25 am
Frank, How are you?
I think the Identities definitions is kept in syscolumns table in user database with status = 0x80.
sp_help yourtable name will show all information you need.
April 27, 2005 at 8:18 am
You may create the encrypted SPs in a dataabse, send the database to your client and let them to import SPs into their database.
It just a thought and never test...
April 27, 2005 at 8:05 am
SQL Server 2005 is able to handle your request. It is not released yet.
April 27, 2005 at 7:33 am
Not I am aware of it.
You can create windows group, add new logins into the group and grant the group to access SQL Server. In this way, you really don't...
April 27, 2005 at 7:31 am
Try uninstall and reinstall.
April 27, 2005 at 7:28 am
It sounds like a security/permission issue. Did you have any error messages?
Check Microsoft KB 269074 for How to Run a DTS Package as a Scheduled Job
April 27, 2005 at 7:21 am
Can you post the error message you receiced when trying to connect to the SQL Server with named pipe?
Did you try to connect MSDE, Named instance or virtual SQL Server...
April 27, 2005 at 7:14 am
How do you define whether your table is not updated in your situation? Maybe you can show some examples?
April 26, 2005 at 3:01 pm
OS administrates system resources and assign the resources to applications like SQL Server which uses and manages the resources assigned to it by OS.
Windows System Resource Manager (WSRM) is available for...
April 26, 2005 at 1:19 pm
I believe we have already answered your question at http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=177197#bm177278
April 26, 2005 at 12:30 pm
1. Try to shut down your application/applications services.
2. Run sp_who2 to see if there are any connections to your database.
3. If some of connections are still there, run "kill yourspid"...
April 26, 2005 at 11:48 am
Which version of SQL Server are you running? I believe everyone here assumes you are running SQL Server 2000.
April 26, 2005 at 11:39 am
Revoke "exec" permission from public role and grant it only to some individuals.
April 26, 2005 at 8:34 am
The last statment from your jobs will be the sp that is still running.
Be remember that users can only see SPIDs they own if they are not 'sa'.
April 25, 2005 at 3:15 pm
Viewing 15 posts - 121 through 135 (of 2,386 total)