on 32bit windows and SQL only recognizes 3GB Physical memory. chances are SQL is using 90% of the 3GB in fact.

Are you running 64 or 32bit?

got it wrong, as the correct answer wasn't listed.

your syntax is wrong in, sequence wouldn't be created to start of with...no increment value, no 'AS'..etc.

if in the same group it should use the new data file.

if you can afford some downtime, i would advise moving the original datafile to the disk with enough...

Autogrow is set on files, not filegroups.

If you add another mdf (data file) enable autogrow on it.

Means the allocated space for the data file, is all you are providing.

NO additional growth can take place on a 100% full data file.

Change autogrow to a value of...

It means 3gb ram is reserved for SQL Server.

When you stop MSSQL - the 3gb is released.

Answer to both Questions:

T-SQL calling proc's...

Yeah, dont think DM is the right tool for your game....

If you have enough disks, best setup would be:

Sys db's on own disk, but have tempdb on its own drive.

user db's on own disk.

split mdf and ldf's as well.

dbo.sysjobhistory

dbo.sysjobs

These tables in msdb contain all job information, join them on job_id.

when you refer to perf counter being missing, where did you look for them?

Perfmon?

Run this query:

SELECT

CONVERT (varchar(30), GETDATE(), 121) as runtime,

dateadd (ms, (a.[Record Time] - sys.ms_ticks), GETDATE()) as [Notification_Time],

a.* , sys.ms_ticks...

a cube is a multidimensional structure of data, consisting of dimensions and meaures.

See it as a very clever and programmable Pivot Table. <- 😎 Yes, I said that.

Good starting point...

we are working in clinet location in banking environment so its not possible from my opinion its very long process to get license to all and if u can share...