Well to keep it simple, it has been observed that SQL Does not deallocate memory with memory pressure as well as in previous versions of SQL Server and Windows (Non R2’s).
So it is a Good Idea to use Min and Max SQL Server Memory Settings with SQL R2 and Win R2
I Just got my hands on the Codenames used by Microsoft even for its products:
http://en.wikipedia.org/wiki/List_of_Microsoft_codenames
I had some interesting Job changes with Twists and Turns…
I Joined T. Rowe Price as a Database Lead and then got an opportunity to work for Microsoft as a Sr. Database Systems Analyst (Which means Sr. DBA).
So I have been occupied with all such change’s and life has been demanding with these new assignments.
Ok This is going to be a small Blog:
Just wanted to mention that you can get performance enhancement with FUSION IO Cards, Which are supported in Win 2003 / win 2008 and Win R2. I have tested them on Windows 2008 x64 and SQL Server 2008x 64
You really get a Significant boost as far as performance goes and kind of creates a new FLASH Memory Tier at the system bus / Kernel Level.
It helped up eliminate any IO related Bottleneck and we had a performance Boost upto 60% (no joke)
I will Give it a Thumbs UP..
Here is the Link to the product site: http://www.fusionio.com/
I am a very critical DBA, when it comes to security and SQL Server is the Far most Secure database i have worked with, but here are some more concepts in SQL Server we can make use of to make the base objects more secure for client apps.
Synonym is an diff or alternative name that is used for a database object. So in turn all the application can use this single part name instead of using the multipart (two, three,four) names for reference a object.
This is also a security benefits in using a synonym for critical database objects, when need not be exposed.
How does this help a client application?
Well if you change the underlying object or structure of the object, you do not have to change the synonym and still use the same synonym name, without worrying about the base object.
The base object can be dropped and replace by the same name object.. like instead of a table you create a view with the same name, the synonym will work.
How to Create a synonym?
FOR Remote Servers (four Part Naming)
CREATE synonym MySynonym for LinkedServer.DatabaseName.SchemaName.TableName
FOR Local Server
Create Synonym MySynonym for DatabaseName.SchemaName.TableName
Select statement for a synonym?
SELECT * FROM MySynonym
How to DROP a synonym?
DROP Synonym SynonymName
So you can say a binding between a Synonym and its base object is by name only.
Synonym can be created on the object types.
Assembly (CLR) stored procedure
Assembly (CLR) table-valued function
Assembly (CLR) scalar function
Assembly (CLR) aggregate functions
Replication-filter-procedure
Extended stored procedure
SQL scalar function
SQL table-valued function
SQL inline-tabled-valued function
SQL stored procedure
View
Table1 (User-defined)
Only synonym owners, members of db_owner, or members of db_ddladmin can grant permission on a synonym.
you cannot reference a synonym that is located on a remote server (linked server)
Synonym can be created only on the following command types:
SELECT
INSERT
UPDATE
DELETE
EXECUTE
Sub-selects
Working on the synonym, affects the base object.
If you insert a Row in the synonym, which in turn inserts a row in the base object.
Read BOL for more info on this as most of the Topic is from BOL.
Oracle says, There is not structural difference between the 2. The only difference is the support policy, where by Oracle Enterprise Linux (OEL) is available as a free download, and RedHat is Available as a Paid download to use in production.
Oracle Enterprise Linux is based on Red Hat Enterprise Linux and is fully compatible—both source and binary—with Red Hat Enterprise Linux as it includes the exact same set of packages at the same version levels with the same source code as the Red Hat distributions. There are approximately 1,000 packages in the distributions. A byte-by-byte comparison of the source code of the two will reveal no difference, the only changes being the removal of trademarks and copyrights.
In order to get Linux support from Oracle, a user does not have to install Oracle Enterprise Linux, if they already have Red Hat Enterprise Linux installed on their systems.
Fully Compatible with Red Hat Enterprise Linux
Oracle synchronizes bug fixes at regular intervals with Red Hat Enterprise Linux to maintain full compatibility. Whenever a new version of an individual package (an errata) gets released by Red Hat, not just as part of an update release, the corresponding package for Oracle Enterprise Linux is made available very quickly, in a matter of hours. If a package has no trademarks and no Oracle specific patches, it will simply be recompiled and reissued for Oracle Enterprise Linux immediately after going through testing.
If a package has trademarks or Oracle Enterprise Linux specific changes, Oracle will examine the source code and compare it against the bug fixes that have been already applied and released as part of Oracle Enterprise Linux. If the Oracle patches are still relevant, then they are reapplied, but if the problems have been fixed in the Red Hat version, whether in the same or in a different way, the Oracle specific patches are dropped and the package recompiled (always checking for trademarks and copyrights issues) and released as part of Oracle Enterprise Linux via the Unbreakable Linux Network (ULN).
References: doc Oracle Unbreakable Linux April 2010. http://www.oracle.com/us/technologies/027614.pdf
Running too much of the Database Tuning Advisor or Index tuning wizard(SQL 2000) on databases can end up “sometimes“ creating hypothetical indexes as the indexes that start with “_dta_index” or “”hind_%”
Too many of the indexes can pose a performance issues for your database. As the issue we had when one of our network admin was trying to be a DBA and worsened things on his end of the database on SQL 2005.
A Quick Clean up of those indexes got back the performance as required.
SELECT *
FROM sys.indexes
WHERE is_hypothetical=1
This Should be run against each database or rather, try the script below.
sp_msforeachdb ‘USE [?]; select quotename(db_name()) as dbname,* from sys.indexes where is_hypothetical=1′
Here is some more useful info from Microsoft. http://msdn.microsoft.com/en-us/library/ms190172.aspx
Which min version do you still work on?
Total Voters: 74
Loading ...