Viewing 15 posts - 1 through 15 (of 57 total)
Yep, that's why I was confused. BOL states 1024 (SQL 7) or 2100 (SQL 2000). My closest choices were 512 and no limit (and the question was about input parameters,...
March 23, 2005 at 7:23 am
Aha, found it:
Index --> Create Procedure:
n
Is a placeholder indicating that a maximum of 2,100 parameters can be specified.
March 22, 2005 at 10:16 am
I have the Updated - SP3 version of BOL.
Under Index --> limitations-SQL Server objects -->Parameters per stored procedure it lists 1024 for SQL Server 7 and 2100 for SQL...
March 22, 2005 at 10:12 am
You could also use DTS (copy SQL Server objects task) to copy the objects without data (there is a Copy Data check box) to a backup database. Then you would...
March 1, 2005 at 8:23 am
Have you looked into Log Shipping to keep the DR servers up to date? I used log shipping to accomplish something similar to what you are talking about.
You could...
February 23, 2005 at 8:21 am
I always created a job to send me an email and set the schedule to run when SQL Server Agent starts. That way I knew when a virtual server failed over...
February 23, 2005 at 8:15 am
If you just want an E/R diagram of your database in Enterprise Manager, expand the database you want to generate the diagram for. There is a Diagrams entry. You can...
February 18, 2005 at 8:14 am
I would perform the migration on a test server and generate your own project plan before I would trust anyone else's. There are too many variables when dealing with a...
February 9, 2005 at 9:00 am
I would also worry about security and "putting all your eggs in one basket."
If you get hit by a SQL Server worm, you've also taken down your domain authentication services....
February 3, 2005 at 8:08 am
I was thinking about putting all of that code in a stored proc, but I wanted to figure out why the code above wouldn't work. It seems like it should....
November 29, 2004 at 1:46 pm
There shouldn't be any problem, but you won't get a performance boost either. Since you said you were just looking for more log space, it should work out great. SQL...
October 26, 2004 at 7:33 am
I was looking for a way to see if the job was stopped and to restart it if it was. I could use a script and just start the job...
October 12, 2004 at 8:36 am
This won't help now, unfortunately, but Yukon (SQL Server 2005) is suppossed to be adding TRY CATCH blocks to Transact SQL.
September 9, 2004 at 10:38 am
The primary keys are already there on the subscriber. What I can't figure out is why it keeps dropping the primary keys on the subscriber during the initial snapshot.
Rob,...
September 9, 2004 at 10:30 am
I looked into queued updates, but it looks like it requires MSMQ. I don't want to further complicate matters with another Server/Service.
Thanks.
September 8, 2004 at 9:51 am
Viewing 15 posts - 1 through 15 (of 57 total)