A woman in a hot air balloon realized she was lost. She reduced altitude and spotted a man below. She descended a bit more and shouted,
"Excuse me Sir, can you help me? I promised a friend, I would meet him an hour ago but I don’t know where I am."
The man below replied, "You’re in a hot air balloon hovering approximately 30 feet above the ground. You’re between 40 and 41 degrees north latitude and between 59 and 60 degrees west longitude."
”You must be an engineer," said the lady balloonist.
"I am", replied the man. ‘How did you know?’
”Well", answered the lady in the balloon, "everything you told me is technically correct, but I have no idea what to make of your information, and the fact is I’m still lost. Frankly, you’ve not been much help to me at all. If anything, you’ve delayed my trip even more."
The engineer below responded, "You must be in Top Management."
”I am", replied the lady balloonist, "but, how did you know?”
"Well," said the Engineer,
"You don’t know where you are, or where you’re going. You made a promise, which you’ve no idea how to keep, and you expect people beneath you, to solve your problems."
maninder
Ok this is a good one. If some one or a DBA has accidently changed the SPACE information on the TEMPDB Database and you get this error while connecting to SQL Server and Performing Queries.
“Could not allocate a new page for database ‘tempdb’ because of insufficient disk space in filegroup ‘PRIMARY’. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. (Microsoft SQL Server, Error: 1101)”
Do Correct this information do this:
ALTER DATABASE TEMPDB
MODIFY FILE (NAME=’tempdev’,FILEGROWTH=10MB)
ALTER DATABASE TEMPDB
MODIFY FILE (NAME=’templog’,FILEGROWTH=10MB)
and the Error should go away at least for you to correct the space issues.
WELL this is for Other Databases too…
As a general Best Practice Rule is to Manage the AutoGrow Feature based on the Space and Memory your Server Has.
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:
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.
Loading ...