Viewing 15 posts - 2,251 through 2,265 (of 5,394 total)
You could disable the constraints, check the data, delete invalid rows and enable the constraints again.
December 5, 2011 at 8:11 am
That's what Pinal Dave seems to suggest.
I've never used it before.
You can enforce the hint using OPTION (ROBUST PLAN) the way you tried.
December 5, 2011 at 7:51 am
Check sys.dm_exec_query_stats, should give you the info you need.
December 5, 2011 at 6:59 am
Ah, my bad, I didn't check things properly.
Maybe this thread will help you:
http://social.msdn.microsoft.com/Forums/en/transactsql/thread/824140a5-0f2b-4254-a69a-6ecdbffe2bb5
December 5, 2011 at 6:37 am
Wit sample data I mean something readily consumable, like this:
SELECT *
FROM (
SELECT 'Systems Team Applications', ...
December 5, 2011 at 6:29 am
Weird, looks like an error you could get from a SQL Server 2000 database.
What compatibility level is your DB?
December 5, 2011 at 6:03 am
Can you please post some sample data and the expected output?
That would make things a lot easier for us.
December 5, 2011 at 5:57 am
SQL Server will use the credentials of the connected user to access the external resources, unless you explicitly impersonate a different user. In the case of a Windows Login, you...
December 5, 2011 at 4:35 am
You're welcome!
December 5, 2011 at 2:59 am
INSERT INTO WestwoodReport SELECT * FROM OPENQUERY(LSCTLRDAT1, 'SELECT * FROM PMSPYP00 WHERE YP_EFFECTIVE_DATE >=1111001 AND YP_Account_No IN (7003303,7003050,7003055,7003013,7002928,8062604,7003306,7002945,7003019,7003006,7003014,7003018,7003307,7002936,8062091,7002897,7003061,8062736,7003064,8062946,7003012,7003057,7003029,7030003,7003314,7003315,7003020,7003017,7003311,7003056,7003329,7002999,7003062,7003024,7003319,7002934,7003063,7002992,7003078,7003323,7003309,7002898,7030010,7002998,2993-01,7003304,7003074,7003317,7003068,7003053,7003067,7003070,7003069,7003073,7003341,7003071,7003320,7003072,7003082,7003088,8062686,7003022,7003065,7002941,7003332,7003084,7030015,7003338,7003302,7003033,7003075,7003015,7003333,7003089,7003085,7003059,7003023,7003349,7003034,7003330,7030014,7003318,7003037,7030017,7003313,7003340,7002946,7003038,7003086,7003087,7003098,7003301,8063443,7003026,1014382,7030013,7030012,7003021,7030019,7030011,7003092,7003030,7003058,7003040,7003031,7003052,7003091,7003308,7003334,7003076,7003079,7003339,7003093,7003353,7003337,1014483,7003066,7003322,7003035,7003095,7030016,7003042,7003094,7003041,7003028,7003097,7003032,7003312,7003036,7003351,7003355,7003016,7003025,7003356,7003356)') AS DB2
December 2, 2011 at 6:47 am
bmw110001 (12/2/2011)
Hi,Ur doing this for sql server 2005 or 2008
I suppose 2005, since this is the 2005 forum.
December 2, 2011 at 5:50 am
This should do the trick:
December 2, 2011 at 4:11 am
When referencing a table variable in a where / join predicate, you need to use an alias.
December 2, 2011 at 3:19 am
Powershell is the answer:
You don't need to be familiar with it, you just need to run it 🙂
December 2, 2011 at 3:10 am
Viewing 15 posts - 2,251 through 2,265 (of 5,394 total)