Viewing 15 posts - 34,336 through 34,350 (of 39,908 total)
Where is your server loacated? The queries run on the server, not the client, so it wouldn't matter from where you run them.
January 28, 2005 at 10:36 am
January 28, 2005 at 10:33 am
In a heavy load, having two log files, perhaps on two disks, can help performance.
January 28, 2005 at 10:32 am
Haven't seen this. Are the mails being sent with just he extended stored procedures? If you send a message from outlook with the same profile does it still happen?
January 27, 2005 at 9:53 am
If you have auditing enabled, you can check the SQL Server error log.
January 27, 2005 at 9:51 am
You can post them here, most of the people that scan the forums use a page that brings them new posts since their last login, so it will be found.
January 27, 2005 at 9:49 am
Any other information? Most likely if the server is up and running that your network is not responsive enough. Are you connecting from EM or QA? You can raise the...
January 27, 2005 at 9:47 am
you are welcome and thanks for the followup. Might help someone else one day if they're searching.
January 27, 2005 at 9:46 am
Depends on who's higher in the food chain ![]()
January 27, 2005 at 9:45 am
Depends on the company. Job Titles are not very tightly coupled to the actual duties anymore. An analyst developer and analyst programmer would be the same in my mind, but...
January 26, 2005 at 10:18 am
That is a stored procedure in your package. You can run this in Query Analyzer to see what the error is.
January 26, 2005 at 10:17 am
Is there a max number of families? You could write self joins with that number of times if you know it. Otherwise you might need to create a temp table...
January 26, 2005 at 10:13 am
sp_who2 will also give you all connections and you can check that for the program name, or workstation name, or login name.
Profiler can be setup to scan for the...
January 26, 2005 at 10:12 am
SQL Server will be slow to release memory. Once it takes it, it tends to hold on. Usually this is mostly for the data cache. You can limit as above...
January 26, 2005 at 10:11 am
Sorry, no experience. Sounds like it might be trying to connect to the wrong port. Is the SQL Server perhaps running on a different port? Check the server network utility.
January 26, 2005 at 10:10 am
Viewing 15 posts - 34,336 through 34,350 (of 39,908 total)