Viewing 15 posts - 16 through 30 (of 80 total)
Hi,
I'm currently London based, I'm a SQL Server DBA/Developer/Consultant with 10 years experience in SQL Server 2000/2005/2008 (I have more information on LinkedIn with regards to my career histroy, please...
August 25, 2010 at 6:20 am
Rather than just capping the amount of RAM SQL Server can utilise I think you should be looking into what is the actual cause of the problem.
Have you gathered any...
June 4, 2010 at 4:45 am
Your welcome.
If the storage side of things is out of your hands, that would be my starting point. Have a look at the failure history for the Maintenance Plan...
June 4, 2010 at 4:32 am
Hi,
I've come across this error type before but only in Visual Studio while manually executing SSIS packages, which kind of makes sense as SQL Server "under the covers" will create...
June 4, 2010 at 4:18 am
Hi,
Another option could be to gather data from the INFORMATION_SCHEMA views on each SQL Server instance onto one server and then write a query to highlight any differences. Using...
June 4, 2010 at 4:04 am
Hi,
I might be totally missing the point here, but wouldn't the following provide the information you require?
select
[UserID],
[Extension],
[Called_Number] [Called Number],
case [Call_Type_Int]
when 3 then 'O/G INT'
when 4 then 'I/C INT'
end [Call Type],
count(1)...
June 4, 2010 at 3:05 am
Hi,
I totally agree with the previous post, providing the disk where the database MDF resides isn't a host for multiple MDFs/other files and by shrinking this particular database as much...
June 4, 2010 at 2:29 am
Keith,
My first port of call would be the restart of the SQL Server Agent as this is actually part of the setup process.
From personal experience I would avoid registry changes...
June 4, 2010 at 2:07 am
Hi Patrick,
That is pretty much correct, as well as having the database on both sides the table schemas must also match.
When a snapshot is created/executed the process creates multiple files...
June 4, 2010 at 1:59 am
The temp table [tempdb_space_usage] is from the perf_warehouse example.
My though process behind sending you that syntax was to hopefully identify some rather large temp tables which you could then cross...
June 3, 2010 at 9:00 am
I would arrange the "bouncing" of the SQL Server Agent as this is part of the Operator/Email Notification setup process, without a restart it simply will not work.
June 3, 2010 at 8:44 am
Patrick,
How frequently does the data change? If the data is fairly static you could create a full database backup of the publication database, manually restore this on to the...
June 3, 2010 at 8:40 am
Just a quick thought before I run through a profiler/Perfmon/custom logging process, assuming you are running SQL Server 2005 or 2008, try running this command:
use [tempdb]
go
select
OBJECT_NAME(object_id) [Object Name],
...
June 3, 2010 at 8:23 am
One option would be to run profiler and log the growth stats for tempdb to a table, you can then correlate any tempdb growth sperts back to a procedure/group of...
June 3, 2010 at 7:52 am
Viewing 15 posts - 16 through 30 (of 80 total)