Viewing 15 posts - 4,636 through 4,650 (of 6,216 total)
You need a command object and a parameters collection. Should find plenty of stuff on MS site. Also a couple articles here:
http://www.sqlservercentral.com/columnists/awarren/reducingroundtripspart3.asp
http://www.sqlservercentral.com/columnists/awarren/introductiontoadothecommandobject.asp
Andy
March 26, 2002 at 12:22 pm
Confirmed permissions on the proc? Are you executing it conditionally?
Andy
March 26, 2002 at 11:08 am
Sorry we didn't get you an answer the first time. Thanks for the follow up and I'll you continue to visit and ask questions!
Andy
March 26, 2002 at 11:07 am
That message is usually right on target. Had it happen to me a couple times when someone in IS inserted a row on the subscriber by mistake, realized it, then...
March 26, 2002 at 11:05 am
As far as I know you have to write to disk then read it back in. I don't the picture control supports the IStream interface. Possibly you could find something...
March 26, 2002 at 8:32 am
You can change to text or ntext, the only time you "might" lose data is if you go from unicode to non-unicode. You can always use full text search if...
March 26, 2002 at 8:27 am
If you're supporting international apps I'd be careful about straying from Unicode fields. If you need a text column, use ntext. If you can get by with the varchar you...
March 26, 2002 at 7:00 am
Setting up a linked server makes it pretty easy, after that plain TSQL will do it.
Andy
March 26, 2002 at 5:27 am
Is the issue the join size or that you don't have a unique ID for the data in both sets to join on? If you have ID's I'd be curious...
March 26, 2002 at 5:25 am
Have you changed your index plan? Deadlocks often center around index access - if you've got an index that is heavily used (and thus effective) trying to add a bunch...
March 25, 2002 at 6:20 pm
Yes, trunc on checkpoint should be false if you're doing log backups. Only thing comes to mind is that they were trying to get the log to shrink, and just...
March 25, 2002 at 6:17 pm
That's correct. N's take twice the space to store the data, Unicode takes two bytes to represent one "character".
Andy
March 25, 2002 at 3:38 pm
Did your original table use varchars or nvarchars? Unicode takes twice as many characters as a plain char.
Andy
March 25, 2002 at 2:26 pm
Sounds like maybe you scripted everything as unicode, using nchar, nvarchar, etc?
Andy
March 25, 2002 at 1:56 pm
Viewing 15 posts - 4,636 through 4,650 (of 6,216 total)