Viewing 15 posts - 48,496 through 48,510 (of 59,102 total)
G.R.Preethiviraj Kulasingham (9/25/2003)
I'll be happy if my scripts are usefull
Please check
http://www.sqlservercentral.com/scripts/listscriptsbyauthor.asp?author=1771
There are many wonderfull tools available in the market....
--Jeff Moden
Change is inevitable... Change for the better is not.
September 1, 2008 at 7:21 pm
So... what "destination" did you have in mind? If it's SQL Server, lookup the "-n" parameter of BCP in Books Online which says...
-n
Performs the bulk copy operation using the...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 1, 2008 at 7:20 pm
thatok (9/1/2008)
I have a table IRchair which has columns staffno and clusterid. I am going to add to this table a clumn named period. So I need to bring...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 1, 2008 at 6:58 pm
rosh (9/1/2008)
Is there any reason for storing data in this manner in the table?
Heh... yep... someone doesn't have a good split function or didn't know how to do a crosstab...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 1, 2008 at 6:55 pm
iam777here4u (9/1/2008)
The problem is, I am using a UDF. I have to use UDF only no store procedures.
Why not?
The problem is that this can't be done in a UDF because...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 1, 2008 at 6:50 pm
Select the count from both and see if they're equal?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 1, 2008 at 6:49 pm
Yes... there are a thousand reasons why this may happen...
1. Code to set the flag to 1 didn't work correctly.
2. Code to reset the flag to 0...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 1, 2008 at 6:47 pm
bumey309 (9/1/2008)
Why is it not recommended to have the database and transaction logs on the same drive? What will be the cause if ever?
The biggest reason is simply performance. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 1, 2008 at 6:39 pm
Jeffrey Williams (9/1/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
September 1, 2008 at 6:35 pm
Christopher Stobbs (9/1/2008)
Type is there for backward compatibility
I wonder why some of the folks from Redmond saw fit to use it to define some of the information schema views if...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 1, 2008 at 6:28 pm
Heh... I'm thinking this is strong justification for tele-commuting. 😛 Let's all become agoraphobic and avoid the epidemic, conspiracys, and a modicum of common sense. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
September 1, 2008 at 6:25 pm
Do like Excel does... do the calculations using FLOAT (Barry implied it with 100.0) and then round the answer to the correct number of decimal points for display. If...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 1, 2008 at 6:18 pm
OpenRowset cannot take variables as part of it's syntax. You'll need to do the whole OpenRowset thing as dynamic SQL.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 1, 2008 at 5:40 pm
As previously suggested, have you looked into "parameter sniffing"? Google it.
Also, are there any settings differences between the two servers like "auto statistics", etc. Last but not least,...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 1, 2008 at 5:38 pm
It could simply be a case of "parameter sniffing"... Google it.
Also, are "auto statisics" enabled or not?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 1, 2008 at 5:34 pm
Viewing 15 posts - 48,496 through 48,510 (of 59,102 total)