Viewing 15 posts - 61 through 75 (of 164 total)
Did you consider Merge replication?
Cheers,
Prithiviraj Kulasingham
http://preethiviraj.blogspot.com/
January 24, 2006 at 6:00 am
Both "Case" and "Or" are attractive to developpers. But I know that in Production they give trouble. My intention is not to prohibit the use of OR (or case) in where clause. ...
Cheers,
Prithiviraj Kulasingham
http://preethiviraj.blogspot.com/
January 19, 2006 at 7:11 pm
Read the first comment by Joe Nakanishi
Cheers,
Prithiviraj Kulasingham
http://preethiviraj.blogspot.com/
January 18, 2006 at 6:55 pm
What do you want to insert when only one condition is satisfied?
If you dont want to insert that row, place what in the where clause.
Hope this is more clear Cheers, http://preethiviraj.blogspot.com/
Prithiviraj Kulasingham
January 18, 2006 at 7:59 am
You can try with sp_ExecuteSql:
DECLARE @sql nvarchar(4000), @val money
SELECT @sql = 'select @val=(329.02 * 1.2) * 1.20'
EXEC sp_executesql @sql, N'@Val money OUTPUT', @val OUTPUT
SELECT...
Cheers,
Prithiviraj Kulasingham
http://preethiviraj.blogspot.com/
January 18, 2006 at 7:54 am
If you use (@READONLY=1 or PublishOnIntra = 1) in the where clause, that clause may not be SARGable. But however, it depeneds on the statistics and you can never be sure. ...
Cheers,
Prithiviraj Kulasingham
http://preethiviraj.blogspot.com/
January 18, 2006 at 7:08 am
Even though you can do something like this to accomplish in one statement, it is not cost effective
WHERE StoryStatus = 4 AND MediaNewsReleaseDate <= GetDate() AND Project = @ProjectID AND...
Cheers,
Prithiviraj Kulasingham
http://preethiviraj.blogspot.com/
January 18, 2006 at 4:26 am
Do you want to insert a default value instead of NULL then add ELSE <DefaultValue> at the end of your case statement (before end)
If you want to limit the...
Cheers,
Prithiviraj Kulasingham
http://preethiviraj.blogspot.com/
January 18, 2006 at 3:48 am
The reason for the second select statement is we dont have an output parameter. when you have a parameter, it will return only one value. In multiple inserts, you may...
Cheers,
Prithiviraj Kulasingham
http://preethiviraj.blogspot.com/
January 18, 2006 at 12:14 am
On Update you will have a problem if the user wants to update soem other column. (without changing the username)
The best option is to use an Unique key on username. ...
Cheers,
Prithiviraj Kulasingham
http://preethiviraj.blogspot.com/
January 17, 2006 at 8:27 am
I suggest that you should add the COid of all instances of ClientOffice in the select statement and keep in the page (May be hidden). Then you can update each...
Cheers,
Prithiviraj Kulasingham
http://preethiviraj.blogspot.com/
January 17, 2006 at 8:12 am
I just saw the reference of User_ID in the code.
The post before will work.
Cheers,
Prithiviraj Kulasingham
http://preethiviraj.blogspot.com/
January 17, 2006 at 7:36 am
Hi Raj,
I am not sure of the logic for User_ID. However, If you are using variables to insert into a table you can insert only one row.
Assuming that @ID...
Cheers,
Prithiviraj Kulasingham
http://preethiviraj.blogspot.com/
January 17, 2006 at 7:34 am
Based on SQL-92 standards, null is not equal to null. (As null means, not defined or unknown) However, SQL Server offers another feature to turn off this option by issueing...
Cheers,
Prithiviraj Kulasingham
http://preethiviraj.blogspot.com/
January 17, 2006 at 5:40 am
Can you add another file into the same filegroup.
I have installed sp4 almost immediately after installation, and I dont have any issues like this.
BTW, do u have full access rights...
Cheers,
Prithiviraj Kulasingham
http://preethiviraj.blogspot.com/
December 6, 2005 at 6:02 am
Viewing 15 posts - 61 through 75 (of 164 total)