Viewing 15 posts - 6,181 through 6,195 (of 6,209 total)
Im definitely against any data type desc in the column name. Where I work, we have an app that uses "foreignkey" for all the foreignkey cols. Guess what it calls...
July 11, 2001 at 6:33 am
Not directly. The only way to keep them out would be to set the db to either dbo only or single user mode, or you could temporarily change their permissions...
July 11, 2001 at 6:28 am
Connection pooling and/or object pooling may be the issue here. I havent had any problems with @@rowcount (have you checked MSDN to be sure though?). I would suggest you test...
July 11, 2001 at 6:26 am
Do you know the stored proc is executing for sure? How about adding some logging to the proc so you can see if it's running and what value was passed?
July 10, 2001 at 10:26 pm
Couple questions. How do you get an int to hold that value? The max value is 2,147,483,648 (or (214) 748-3648 as a phone number!) Another question is why did you...
July 10, 2001 at 10:23 pm
Easiest way would be to run Profiler while you create the package, that should give you the list without too much work!
July 10, 2001 at 10:13 pm
Honestly I dont know:-) I think the package will run ok, the question is how will the data look. You might want to pull some data out of the db...
July 10, 2001 at 2:10 pm
Im not sure I agree with a separate drive for the pagefile. I know it's recommended, but if you're even close to properly configured, you shouldnt be hitting the page...
July 10, 2001 at 11:04 am
They should all execute independently, assuming that running one doesn't cause another to be blocked by locking of the data. Not impossible, but I think 1000 at once would be...
July 10, 2001 at 11:01 am
If you're using SQL2K you could just change the collation to match the old one.
July 10, 2001 at 6:36 am
You cant use the results of a stored proc directly in TSQL (ADO is often a better choice for these types of things). The easiest way to do it in...
July 9, 2001 at 8:02 pm
We keep ours local, data on fibre. Nice and simple, plus good separation if you're having a problem with your storage.
July 9, 2001 at 7:59 pm
I'd vote for the SQL dump to disk as well. Easy and reliable.
July 9, 2001 at 7:56 pm
I've got some sample code posted in an article http://www.sqlservercentral.com/columnists/awarren/dmointro.asp that you may find helpful, plus a couple other articles on DMO, including one about how to restore.
July 9, 2001 at 7:55 pm
Sorry we didnt get back to you in time. If you're connecting to a server via Query Analyzer to do the restore, it's pretty much like you're standing in front...
July 9, 2001 at 7:53 pm