Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
rob41
Yak Posting Veteran
67 Posts |
 Posted - 2010-12-27 : 16:09:31
|
| what is the correct way to setup a schema. The default is dbo.(name of table) but when it was created this way it did not work with visual studio (I need to have the ability to automate jobs). We got it to work by creating a schema that had my company name\myname and then everything works. I think this might be the wrong way to set it up. We are trying to correct errors in the way the database was setup on a development server. Does anyone have any sugestions on doing this the right way. |
|
|
jeffw8713
Aged Yak Warrior
819 Posts |
Posted - 2010-12-27 : 18:42:37
|
| Normally, everyone uses the dbo schema for all of their objects. I am not sure why you say this did not work for you - or what issues you are having.Can you provide more details on those issues?Jeff |
 |
|
|
nigelrivett
Master Smack Fu Yak Hacker
3385 Posts |
Posted - 2010-12-27 : 20:43:32
|
| The way you have it means that it is bound to your username. Presumably only works because you are developing nd won't work for anyone else - what happens when you leave the project or company.Suspect you are trying to use dev studio integrated with sql server and have done something odd wit the integration. I would just use management studio for creating objects in scripts and run the scripts. Keep everything in a source control system and then you shouldn't have issues.But then I suspect you wil have more fundamental design issues.==========================================Cursors are useful if you don't know sql.SSIS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
|
|
|
|
correct way to set up schema in database