Viewing 15 posts - 33,646 through 33,660 (of 59,099 total)
SQL Server Youngling (5/27/2011)
"For an optional solution, please refer to the following URL"
Optimal, perhaps?
And...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2011 at 9:04 pm
David Jackson (5/27/2011)
SQL Server Youngling (5/27/2011)
"For an optional solution, please refer to the following...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2011 at 9:02 pm
JAYANTH KURUP (6/13/2011)
For obvious reasons you should try never to use an OLTP database back end as the data source for your reports.
"Never" is a pretty strong word here. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2011 at 8:23 pm
Grizzly Bear (6/13/2011)
This table had 35 Million Rows.
We were Updating the BitColumn Field.
There was also a Trigger which would write to another table, which...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2011 at 8:15 pm
toddasd (6/13/2011)
Jeff Moden (6/13/2011)
sql_jr (6/13/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2011 at 7:52 pm
vultar (6/10/2011)
Just a suggestion as well. The original post doesn't mention anything about the need to automatically detect the names of over 100 servers..
Absolutely true. But I also didn't...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2011 at 7:37 pm
Lowell (5/26/2011)
can you turn off trustowrthy, change the proc to WITH EXECUTE AS SELF,...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2011 at 7:08 pm
Shabba (5/27/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2011 at 7:01 pm
Ah... almost forgot. You might want to take a look at Michael Valentine Jones' post above... the concept of using the underlying "date serial number" (number of days since...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2011 at 6:22 pm
No... following your standard of having an ID column on most tables, leave the PK on the ID column (makes some forms of automation a lot easier). Just drop...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2011 at 6:14 pm
chas.clarke (6/13/2011)
Thanks for coming back.
I am trying to combine several stored procedures and functions into one query that I can run with my limited access. Initially, whilst I refine...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2011 at 6:08 pm
MtnJim (5/26/2011)
Thank you so much. I was tearing my hair out trying to figure out why my division wouldn't work.
Ah... you bet and, again, apologies for the late response. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2011 at 6:04 pm
robertm-772679 (10/19/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2011 at 6:00 pm
jmaloney-1117255 (6/7/2011)
I suspected that there would likely be some overhead involved. And thank you for the links, I'll check...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2011 at 5:50 pm
Roy Ernest (6/15/2011)
Steve, I will expecting you for sure. Trey, there is lots of time to save money for the trip....
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2011 at 5:38 pm
Viewing 15 posts - 33,646 through 33,660 (of 59,099 total)