Viewing 15 posts - 13,276 through 13,290 (of 13,838 total)
Try this - untested, but should get you going:
select r1.*
from server1.database1.information_schema.routines r1
left join server2.database2.information_schema.routines r2
on r1.routine_name = r2.routine_name and r1.routine_type = r2.routine_type
where r1.routine_type = 'procedure' and (r2.routine_name is null)
October 3, 2005 at 10:46 am
Why not just detach the dbs on the old computer, copy them across using Explorer and then attach on the new PC? This takes SQL Server out of the equation.
Also,...
October 3, 2005 at 7:26 am
Using EM to input data, CTRL/0 will enter a NULL for you.
If you are really concerned, I guess you could write a trigger that will always convert space to NULL,...
October 3, 2005 at 5:42 am
SQL Server recognises a space as being different from a null (because it is). Why don't you just configure your app to convert a space to a null and write...
October 3, 2005 at 4:20 am
Can't find a way of doing this without using sysfiles - here's an example, if you need it:
declare @dbname varchar(100)
declare @strSQL nvarchar(500)
set @dbname = 'master'
set @strSQL = 'select name, fileid,...
September 25, 2005 at 6:01 am
What you are trying to do is a little more complex than this - though this gets a bit closer, I think:
declare @table varchar(50)
declare @str1 nvarchar(1000)
set @table = 'test_table'
set @str1...
September 25, 2005 at 2:49 am
I've never seen this message before - you've got something strange happening there! All I can suggest is that you remove transformations one at a time and keep trying ......
September 23, 2005 at 2:45 am
If you are writing the code as part of an ActiveX script, the & character is used to concatenate strings, not + (just to keep you on your toes)!
September 22, 2005 at 6:09 am
Suggest you modify your queries to remove any likelihood of ambiguity between column names. Do this by prefixing the column name with the table name:
select tablename.columnname from tablename
If the table...
September 22, 2005 at 2:36 am
You can check this easily in EM. Just open Security/Logins, right click the user of interest and select properties and you will see the default database.
September 21, 2005 at 1:09 pm
You will not achieve this type of formatting with straightforward SQL statements - Ray M's solution, possibly with an additional ORDER BY clause so that you get everything in date...
September 21, 2005 at 1:03 pm
update no
set status = 2
from n_order no join n_inv ni on no.id = ni.id
where (ni.tf is not null or exists (select bt.debtkey from banktable bt where bt.debtkey = ni.debtkey))
September 21, 2005 at 12:54 pm
You haven't said what you want to update and what value, so I have left these for you to complete.
update no
set [field] = [whatever]
from n_order no join n_inv ni on...
September 21, 2005 at 12:02 pm
Sure - right click on the Transform Data Task, select properties and then click on the Options tab. You will see Max Error Count about halfway down the dialog box.
September 21, 2005 at 10:14 am
Don't be offended if this is blindingly obvious to you, but does the PHCR_Record table have an IDENTITY column defined?
September 21, 2005 at 2:55 am
Viewing 15 posts - 13,276 through 13,290 (of 13,838 total)