Viewing 15 posts - 46 through 60 (of 2,386 total)
I think you need a good recovery plan, lost of one week productivity is way too much and unacceptable to me.
How large is your database?
May 11, 2005 at 8:11 am
Since you are able to run package using dtsrun outside SQL Server, It looks like you need to increase the memory reservation in SQL Server process with paramemter -g for...
May 10, 2005 at 1:26 pm
I don't think multiple instances will help. Instaed, I think it may become even worst since the workloads remain same.
May 10, 2005 at 12:59 pm
DBCC Shrinkfile can shrink the log file to any size you want.
May 10, 2005 at 12:52 pm
Is it a dedicated SQL Server or other applications also run in the same server?
You have to figure which processes are taking away your resources (CPUs, Memory etc), It may...
May 10, 2005 at 12:44 pm
There is no way for SQL Server 7.0 to use the memory above 4GB.
May 10, 2005 at 12:40 pm
Try to login it with OSQL.exe and run sp_helpdb to find out the database name.
You can get it from EM if you have other SQL Server installations.
Run sp_who2 to find...
May 10, 2005 at 12:31 pm
What is your database recovery mode currently?
If it is in FULL recovery mode, you have to setup a job to backup the transaction regularly.
You can also change it to...
May 10, 2005 at 12:29 pm
Did you enable /3GB at same time with "AWE"? Are all instance run i same physical server or in different nodes?
May 10, 2005 at 12:15 pm
When you issued statment to query 32 bit linked server from 64 bits server, the query is looking for stored procedure sp_tables_info_rowset_64 in 32 bit server and it doesn't exist.
What I...
May 10, 2005 at 11:48 am
I have no issue to link my 64 bits server to 32 bits one, try to link to another 32 bits server to see you still have same errors.
May 10, 2005 at 8:40 am
In addition to add more memory, you may also consider
1. How do you configure the disk system, what type RAID do you have?
2. How do you allocate the database and...
May 10, 2005 at 8:38 am
Try use Profiler to trace which stored procedure is not found.
May 10, 2005 at 8:17 am
Long PAGEIOLATCH waittype mostly indicates I/O subsystem bottleneck, Check whether you have high disk queue length from perfmon.
May 10, 2005 at 8:09 am
Yes you can with some tricks but you can only use global temp table. Create the the temp table from QA first, then create "execute SQL task" that create a temp table...
May 6, 2005 at 7:06 am
Viewing 15 posts - 46 through 60 (of 2,386 total)