Viewing 15 posts - 76 through 90 (of 97 total)
Yes you could. Install MSSQL 2k as a named instance and leave version 7.0 as the default instance. However, you will need to have separate copies of your...
July 22, 2003 at 6:47 am
Are you doing this in a trigger? INSERTED is not available outside a trigger.
July 21, 2003 at 8:05 am
Something like the following code is what you want.
SELECT EMPLEAVE.* FROM EMPLEAVE
left outer join EMP on EMPLEAVE.Empcode = EMP.Empcode
Where EMP.Empcode is null
July 21, 2003 at 7:59 am
You could create a DTS package to do this or you could write a script. Either way, there is no automatic table split.
July 21, 2003 at 7:43 am
Couple of things: How are you passing your @OldName variable? For column change this should be 'tablename.oldcolumnname' for sp_rename to work.
Also, under what security context is your dotnet...
July 21, 2003 at 7:38 am
Check your @recipient variable when the package fails. Probably the email address is longer than 50 characters allow in the variable. In which case a truncated (and therefore...
July 21, 2003 at 7:23 am
Check out sp_setreplfailovermode in BOL.
July 16, 2003 at 5:55 am
SQL Server 2000 provides a secure administrative link between the Distributor and Publisher and I don't think changing the password of the account under which SQL Server runs has any...
July 11, 2003 at 8:25 am
Keeping the two databases synchronized require the use of Replication. Look at transaction replication with immediate updating subscriber. You could find the how-to in BOL. Cheers.
July 11, 2003 at 8:16 am
Hey, see my answer to your post in the Administration forum. Cheers.
July 11, 2003 at 8:11 am
There is no way you could migrate your stored procedure codes straight from SQL Server into Oracle. For one, the codes are probably not compatible and you would have...
July 11, 2003 at 8:08 am
SET ANSI_NULLS is a database option and you could set it on or off at anytime. Use sp_dboption or (as advised by microsoft) use ALTER DATABASE command. You could...
July 11, 2003 at 7:53 am
I have come across this problem many times. I have never been able to determine the cause (probably a bug in the way security information are passed to the package...
July 11, 2003 at 7:34 am
Have you checked the "SQL Server Properties (Processor Tab)" options to confirm that you have correctly set the number of processors to use for parallel query as well as the...
July 7, 2003 at 6:52 am
Viewing 15 posts - 76 through 90 (of 97 total)