Viewing 15 posts - 51,916 through 51,930 (of 59,102 total)
Kiran,
I recommend that you spend a couple of hours reading about indexes in Books Online (comes free with SQL Server). Start by reading "Indexes, Overview" in the index tab...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2008 at 5:49 am
Almost forgot... as of SQL Server 2005, SQL Server can also use a form of Try/Catch. I'd don't use it because I never got into "programming by exception" because...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2008 at 5:39 am
You can either raise a "success" error or have the app process the "RETURN" code, or both...
CREATE PROCEDURE sales.up_EmpDelete
@SSN CHAR(9)
AS
--=====...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2008 at 5:36 am
You need to use a BCP format file. See Books Online for how to build one... it's not that hard.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2008 at 5:19 am
Don't use either terminator in the code... the defaults are probably correct for your single column text file.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2008 at 5:16 am
Sarvesh Kumar Gupta (3/11/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2008 at 5:13 am
Note that it matters, but I like that vertical format better. More closely resembles even preformatted hard-copy schedules.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2008 at 5:06 am
Doesn't matter who's on what... shrinking a database should not be done just as a matter of fact either automatically or by scheduled task.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2008 at 4:58 am
Yes, that would be the safe guard... but, I recommend that you don't rely on that safeguard as a programming tool... takes a comparitively long time to have an error...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2008 at 4:52 am
It's the same mistake that many make... GOOGLE "3rd Normal Form" to find out about database "normalization" and why it's important despite the fact the you might have to join...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2008 at 4:42 am
Heh... If I remember correctly, it's called "Agile" programming... and it sucks. I no longer wait for sp1 to upgrade... now I wait for sp2.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2008 at 12:31 am
You don't need both... Primary Key is a unique index that doesn't allow nulls.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2008 at 12:27 am
Best thing to do is to look them up in Books Online. Bottom line is, if they work, then it's probably a good thing... if they don't work (as...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2008 at 12:07 am
My apologies... I just remembered something and I verified it in Books Online... you don't need to set Trunc. Log On Checkpoint because the SIMPLE recovery mode does it for...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2008 at 12:05 am
I have the auto shrink on. I
That's probably one of the worst things you can do... you are fragmenting the database and fragmenting the physical files on disk. Everytime...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 11:59 pm
Viewing 15 posts - 51,916 through 51,930 (of 59,102 total)