Viewing 15 posts - 181 through 195 (of 236 total)
Do you have any UPDATE triggers between the two tables?
If it ain't broke, don't fix it...
December 7, 2005 at 3:35 am
Hi,
I have solved one part of my problem
There IS a timeout setting when executing remote stored procedures. On the Properties dialog of the...
If it ain't broke, don't fix it...
December 7, 2005 at 3:24 am
Hi
I have a similar problem. Since I have standard edition I have written my own log shipping routines which work fine all week. Every night there is a full backup...
If it ain't broke, don't fix it...
December 6, 2005 at 2:03 am
The Matrix. I first watched the Matrix on a flight from London to Atlanta, and at the end of it I was left with a distinct feeling of 'what if...
If it ain't broke, don't fix it...
December 5, 2005 at 2:39 am
Thanks for a great article which clearly explains the balance between isolation and concurrency. I have had to make extensive use of (NOLOCK) in reports to obtain good conurrency because the...
If it ain't broke, don't fix it...
December 5, 2005 at 2:28 am
I thought standby could be used with either, certainly it doesn't cause any problems when I include it in the restore command run from query analyzer. I tried the command...
If it ain't broke, don't fix it...
November 22, 2005 at 1:51 am
No doubt we will soon have books being written on-line, a page or chapter at a time, 'open source' style, with contributions from the readers.
David
If it ain't broke, don't fix it...
November 21, 2005 at 4:19 am
If I understand you correctly, you are storing your SQL statements in Table10, and retrieving them to the variable @s-2 before executing them with exec sp_executesql.
Is it that you want...
If it ain't broke, don't fix it...
November 2, 2005 at 2:27 am
Me too,
I usually either end up concatenating columns to get the required condition, or using WHERE EXISTS.
Didn't know that the correct name for these was 'row constructors' 
If it ain't broke, don't fix it...
October 6, 2005 at 2:58 am
Hi
I was wondering if you could build a SQL statement that used a JOIN and a searched CASE to generate the different columns instead of all the inline SELECTs. It might make...
If it ain't broke, don't fix it...
October 5, 2005 at 2:49 am
Logins assigned the system administrators (sysadmin) server role will automatically create objects belonging to dbo (look under dbo in BoL).
David
If it ain't broke, don't fix it...
October 4, 2005 at 2:40 am
Also worth checking the instance name on your old computer. If you have ever upgraded or re-installed SQL Server on the old machine you may need to specify the instance...
If it ain't broke, don't fix it...
October 4, 2005 at 1:37 am
For a warning about taking this approach to extremes, see Don Peterson's article on Lookup Table Madness...
http://www.sqlservercentral.com/columnists/dpeterson/lookuptablemadness.asp
If it ain't broke, don't fix it...
September 27, 2005 at 1:06 am
Hi,
if you are trying to backup the file to a folder on another server then I suggest you create a shared folder on that other server, and give the account...
If it ain't broke, don't fix it...
September 26, 2005 at 2:38 am
Hi,
there are two forms of CASE statement described in BoL,
Simple CASE, which yields a single column with different values depending on the results of the expression.
SELECT
CASE <expression>
WHEN <condition1> THEN...
If it ain't broke, don't fix it...
September 26, 2005 at 2:10 am
Viewing 15 posts - 181 through 195 (of 236 total)