Viewing 15 posts - 121 through 135 (of 185 total)
The error message is self-descriptive:
The product level is insufficient for component
You don't have SQL Server Integration Services (SSIS) installed, but Database Services have limitation to ran SSIS packages.
One of...
September 19, 2009 at 10:50 am
You will not interrupt production and you don't need to switch applications manually to the Passive node. This is main point of cluster - your cluster still have the same...
September 19, 2009 at 10:30 am
In Active/Active cluster you need to do all mentioned steps.
In Active/Passive some people recommend install SP on the Active node only. I disagree, because any other services, like SSIS, SSAS...
September 19, 2009 at 10:27 am
There are several ways, but I would create 2-step job using your 2 scripts and put something like
if (select count(*) from FROM [ReorderS]) > 0
in the beginning...
September 19, 2009 at 7:32 am
You can shrink the tempdb data files and log files
it might release some space
Hmm... It looks like it is not a real option in this case. For doing that...
September 19, 2009 at 7:09 am
Script your job into new window of QA, add new code and run the script - your job will be re-created with new step.
September 19, 2009 at 5:33 am
Wow! Your question requried very big and detailed answer.
If you google "how to move sql server 2005" you get more than 2 million results.:-)
September 19, 2009 at 5:00 am
Here is the answer for your question #1
1. Connect remotely to the first node of your cluster through the Terminal Services by a physical box name
2. Copy an installation package...
September 19, 2009 at 4:42 am
Why you are talking about SP2? SP3 is the latest patch now.
September 19, 2009 at 4:41 am
In the future you have to have the TempDB log file size restricted at certain point, do not allow unlimited grow.
Now I would just restart SQL Server services if it...
September 19, 2009 at 4:32 am
In this case you may want to create AFTER trigger on the whole database and catch all structural modifications into audit table.
September 18, 2009 at 1:27 pm
You may want to use DDL trigger on that table.
It could be INSTEAD OF or AFTER trigger.
"INSTEAD OF" trigger will prevent any ALTER TABLE operations, but "AFTER" trigger can catch...
September 18, 2009 at 1:10 pm
Here is how to check it through Registries:
The version information is found in the following key:
HKEY_LOCAL_MACHINE\Software\Microsoft\DataAccess\FullInstallVer
To check the registry, follow these steps:
On the Start menu, click Run.
In...
September 18, 2009 at 12:57 pm
It is not about version. The only way to find MDAC is verify the version. If you see the version, something like 2.0, that means you have it installed.
This is...
September 18, 2009 at 12:53 pm
NAtive client is application's requirement.
Yes, I understand. I am just think it is already installed with MDAC.
There are two different ways to check which version of Microsoft Data Access Components...
September 18, 2009 at 12:43 pm
Viewing 15 posts - 121 through 135 (of 185 total)