Recent content by Mich

I own several asp/jsp systems that tend to get, for lack of a better word, "clogged" with cache. When a problem is reported the first response is "Have you closed all browsers and cleared all cookies (CABACAC)?" Unfortunately many of my users will have a dozen sessions open with mutliple tabs...

I'll check that out. Thanks for the tip. The server isn't retiring, we're just being moved to another one. -If it ain't broke, break it and make it better.

We are migrating to a new SQL box and have to point hundreds of reports to the new server. Is there a way to script this? -If it ain't broke, break it and make it better.

I have a package that executes successfully, but throws up the following error: Error: The connection "050262" is not found. This error is thrown by Connections collection when the specific connection element is not found. Now, I may have set up connection "050262" at some point during...

You should upgrade from MSDE. Can you connect via EM using mixed authentication? -If it ain't broke, break it and make it better.

I've never seen, or heard of, more than one database in a BAK. However, you can run this to make sure, restore headeronly from disk = '<filename>' -If it ain't broke, break it and make it better.

Is that enough? The situation I ran into happened because large amounts of data was being added to the db between 3 and 4 pm every day. The db had been set to a small initial size and Autogrowth was set to 2% (don't ask me why). That meant the db was bogging down every day between 3 and 4...

Do you have 'Autogrowth' enabled on the db's in question? I've run into situations where this has caused problems similar to this. -If it ain't broke, break it and make it better.

Ahhh, I'm onto you now. The extract scripts are vendor generated and I have been trying to test with a caller script. I need to modify the extract scripts to write to a file reporting when their done. Let me test this. -If it ain't broke, break it and make it better.

What is the code for your trigger? -If it ain't broke, break it and make it better.

Well, it isn't so much to test the server's CPU performance or the database's performance as it is to test the script's performance. The determining factor is time to run which includes the performance of the server, db, etc. If I run all of the scripts against the same db then I'm introducing...

Yeah, that is what I'm doing right now. I was trying to avoid it because now I have to install 140 instances of SQL. -If it ain't broke, break it and make it better.

Profiler might work, but you'd need to have it running 24/7 to catch the "perp". That or know exactly when they are going to drop the linked server. You can use DDL triggers. Here is some good info => http://www.sql-server-performance.com/articles/audit/ddl_triggers_p1.aspx -If it ain't...

They are all connecting to separate databases and writing their own files. The concern I have is the load that will be placed on the server launching the scripts when they are all ran at the same time. It's been my experience that scripts, especially those that write to text files, tend to be...

msdb.sysjobs_view A little script I use often. select sjv.name as Name, max(sjh.run_date) as LastExecution, sjh.run_status as ExitCode from sysjobhistory sjh join sysjobs_view sjv on sjh.job_id = sjv.job_id group by sjv.name, sjh.run_status -If it ain't broke, break it and...