189 reputation
16
bio website info-arete.com
location
age
visits member for 2 years, 2 months
seen 2 days ago

I spend a fair amount of time querying, reviewing, and visualizing data for projects large and small; once in a while, I write about it, too.


Apr
15
comment sql server 2000: no longer able to expand jobs in sql server agent
@StevePettifer - Queries against msdb.sysjobhistory and msdb.sysjobs run fine in query analyzer.
Apr
15
comment sql server 2000: no longer able to expand jobs in sql server agent
@AaronBertrand - When I connect to the server, I do not experience lag time; when I open a table or open a proc, I do not experience lag time; when I run a basic query, I do not experience lag time; yet whenever I attempt to view the Job Details under SQL Server Agent, the lag time is significant.
Apr
15
comment sql server 2000: no longer able to expand jobs in sql server agent
@AaronBertrand - RDP into the 2000 box indicates the same slowness for SQL SErver Agent jobs display.
Apr
15
comment sql server 2000: no longer able to expand jobs in sql server agent
@AaronBertrand - Connectivity is good. msdb.sysjobhistory shows about 6500 records, with 90% of the records having been created in 2014.
Apr
15
asked sql server 2000: no longer able to expand jobs in sql server agent
Jan
17
asked Scheduled copy of large table from SQL Server 2000 to 2008
Jun
18
accepted Query mail logs for xp_sendmail
Jun
18
comment Query mail logs for xp_sendmail
@AaronBertrand - xp_SendMail.
Jun
18
asked Query mail logs for xp_sendmail
May
20
awarded  Constituent
May
20
awarded  Caucus
May
6
accepted maintaining full text index on large table
Apr
26
revised maintaining full text index on large table
added 429 characters in body; edited tags
Apr
26
asked maintaining full text index on large table
Mar
10
revised table design to track significant events associated with an item
further clarification
Mar
10
comment table design to track significant events associated with an item
@AaronBertrand - yes, in this case, each event can only happen once for an order. I failed to make that clear in the original post.
Mar
10
comment table design to track significant events associated with an item
@AaronBertrand - just looking for clarity. Since you went through the trouble of specifying primary and foreign keys in your examples, is there a reason you did not make the EventID and OrderID a clustered primary key? Sorry if I'm being a pain - I do appreciate your guidance.
Mar
9
awarded  Commentator
Mar
9
comment table design to track significant events associated with an item
Yep, thanks for the reminder. Still curious, though, if you know of the edge cases where it would be good not to normalize up front?
Mar
9
accepted table design to track significant events associated with an item