Viewing 15 posts - 16,816 through 16,830 (of 19,564 total)
Jack Corbett (3/5/2010)
March 5, 2010 at 10:30 am
Grant Fritchey (3/5/2010)
I recently interviewed at a company where it was made pretty clear, just how little I know....
March 5, 2010 at 10:26 am
Lynn Pettis (3/5/2010)
March 5, 2010 at 10:19 am
Jack Corbett (3/5/2010)
March 5, 2010 at 9:20 am
You're welcome
March 5, 2010 at 9:07 am
What you describe is similar to what would happen if the public role had been locked down.
Here is an article that discusses security and locking down sql server.
http://duartes.org/gustavo/articles/Lock-Down-SQL-Server-2005.aspx
March 5, 2010 at 12:12 am
Some resources:
March 5, 2010 at 12:02 am
It seems that the application and database are competing for resources - memory being a good contender.
What are your memory settings for sql server?
Also, I would tune your sql queries...
March 4, 2010 at 11:57 pm
Has anybody locked down the public role?
March 4, 2010 at 11:52 pm
Henrico Bekker (3/4/2010)
Also depends on the needs of...
March 4, 2010 at 11:48 pm
This will eliminate the "NOT IN"
with apples as (Select [name] from tablename where fruit = 'Apple')
Select distinct t.Name
From TableName T
Left Outer Join apples a
On t.name = a.name
Where a.name is null
March 4, 2010 at 11:46 pm
I can tell you that a bare minimum ability to understand at a basic level is necessary. Being able to look at .Net code and understand what it is...
March 4, 2010 at 11:41 pm
It depends on whether you need to or not.
Will it be beneficial - sure.
You can apply what you learn in .Net to CLR procedures and to SSIS packages. Both...
March 4, 2010 at 11:35 pm
Viewing 15 posts - 16,816 through 16,830 (of 19,564 total)