network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 11 months |
| seen | Aug 24 '12 at 0:00 | |
| stats | profile views | 0 |
I'm a developer hailing from sometimes sunny Wellington, NZ. I specialise in web development with C#, ASP.NET, MVC.
|
Nov 29 |
awarded | Teacher |
|
Jun 30 |
comment |
Empty tables in WSS 3.0 configuration database It's a WSS3.0 installation. Totally vanilla running on Windows Server 2003. I ended up using the SPM2007 app mentioned above and it worked wonderfully. I think the issue is really that I didn't understand how the database is laid out. What I think I was actually looking at was the empty tables that would be used if I was upgrading from WSS 2.0 to 3.0. I suspect the upgrade process takes the data that does exist in those tables in 2.0 and then "collapses" them down into XML objects in the dbo.Objects table. |
|
Jun 20 |
comment |
Empty tables in WSS 3.0 configuration database I wonder if this is the standard database layout for the WSS 3.0 and above. I've had a look at some 2010 databases and they are the same. It seems the core info is actually all housed in the dbo.Objects table. |
|
Jun 20 |
comment |
Empty tables in WSS 3.0 configuration database Thanks for the SPM 2007 link! I'll see if it sheds any light on the problem. |
|
Jun 20 |
answered | What is the recommended way to query data on a Sharepoint site? |
|
Jun 20 |
asked | Empty tables in WSS 3.0 configuration database |
